Can’t we just use the WSDL generated by the Database Adapter also for the proxy service? It would be possible, but by that, we would expose information from the database to the outside and by that create a much stronger coupling between the service consumer and the database than necessary.
We would use a contract-last approach, where the contract is just generated based on some artifacts already available!
No more copying of files between the two projects is necessary! I will use the Database Adapter to access the data, wrap it by a business service and use a proxy service with two XQuery transformation to publish it as a SOAP Web Service with its own WSDL and XSD. I’m using the notation from our Integration Blueprint book.
Some of the older sample available on the Web show how to use the OSB console to import the artifacts generated by the adapter. By that the data is immediately available to any SOAP Web Service consumer. In order to follow the tutorial below, the following software has to be available: This finishes the work in JDeveloper.
In that path, create a DWORD key with the name “Enable Out Of Proc Build” and set it’s value to “0” (zero). Why not reach little more and connect with me directly on Twitter, Facebook, Google and Linked In.