Create jcd from wsdl
Is it possible, given a provided wsdl, to create a web service java collaboration? The docs seem to show a web service being created from a wsdl in eInsight, but can it be done without eInsight?
Is it possible, given a provided wsdl, to create a web service java collaboration? The docs seem to show a web service being created from a wsdl in eInsight, but can it be done without eInsight?
No, to my knowledge this capability is not available
Yes, you can. You create a Web Service Definition (akin to a WSDL OTD) and then call the appropriate operation from inside a JCD (just like you would call the write() method on a File OTD). You create the Web Service Definition by following the [File --> Import --> Web Service Definition] menu option in E Designer.
There is some literature about this in eGate User's Guide for 5.1.3 - section 13.4 - page 486.
I probably didn't explain the scenario very well.
I think what you are describing is calling (invoke()) a web service from within a jcd, that is being a client. As you say the wsdl otd can be created by importing a wsdl, and then used in the jcd.
What I am after is creating a web service server jcd from a wsdl; the reverse of creating a new web service jcd and generating the wsdl.
It is not possible in all 5.x versions through 5.1.3.
Hi,
I was also searching for such a functionality. It seems that there is really no solution provided by JCAPS. Does anybody know if future versions will support this in my opinion basic functionality for a SOA Suite?
A work around would be to use other IDEs to create a Java Web Service and than use this web service inside JCAPS.
This also solves the problem, that a JCD can only implement one operation.
For example the Sun Enterprise Studio can import a WSDL and creates the corresponding java classes.
Best Regards
Fabian Meier
Use eInsight, which is the Java CAPS component intended for web service orchestration. eInsight buinsess processes can both be exposed as web services and can consume web services using WSDL definitons as the basis for client and provider implementations.
Java CAPS is just fine as a SOA suite if one uses the correct parts of it for the job that needs doing..
Message was edited by:
mczapski