Jul 3rd, 2007, 07:36 AM
Steps to implement 3rd-party WSDL endpoint?
What is prefered way to implement or connect to as client to some 3rd-paty web service which is defined by XSD and its WSDL?
Lets' say this 3rd party published WSDL and XSD for its web service. I know I can use O/X marshalling generator libraries such as JAXB to create classes from some XSD, but what with WSDL since I cannot see any wsdl2java generator?
Should I read manually this WSDL so to find out what are URLs like where I should connect to (client), and also read it so to know on what URLs I should publish some operations/ports when wanting to implement this web service (server) ?
Jul 3rd, 2007, 07:40 AM
Just to make myself clear - is it necessary to read manually this WSDL, so to find out URLs and information about ports/operations where I should publish this WSDL-defined service?
Jul 5th, 2007, 01:38 PM
Generating client classes using soapUI
Find here some solution for generating the client classes.
using soapUI(available as a plugin for eclipse) you can generate client classes from WSDL files.Here you can find so many options such as using Axis,JAXB,JBOSS and so many.
I think you can easily do this
Jul 7th, 2007, 02:53 PM
For now, you have to manually extract the xsd:schema part from the wsdl, and feed it to a code generator like JAXB's xjc. And the url has to be extracted as well, to use as the defaultUri property of the WebServiceTemplate.
We might improve this in the future, but for now that's the way it works.