Skip to main content

ADF to service enabled bindings : findings

Service enablement
It is very easy to expose your adf code in any application module as services with just a couple of clicks.
(Although this may not be the best thing to do without thought)
This could allow you to leverage your existing investment in ADF and publish the existing code
as needed to your SOA enviroment.

EO bindings
You can base Entity Objects on services and have all the same rich functionaltiy adf provides yet using a service backed entity.

Webservice data control
This control allows you to incorporate web services in any ADF page simply and quickly

Pojo custom control
This allows you the most flexibility you can create a custom data control off a pojo and use this to call you web services.

With these tools you can integrate any third party or internal services into your adf application quickly and easily.
All in all I was pleasantly surprised with the service integration in ADF.
Although there are a couple of things that where tricky (custom LOV's etc) you should be able to achieve
what you need with the minimum of fuss.

Comments

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]