You cannot – a XSD describes the DATA aspects e.g. of a webservice – the WSDL describes the FUNCTIONS of the web services (method calls). You cannot typically figure out the method calls from your data alone. These are really two separate, distinctive parts of the equation. For simplicity’s sake you would often import your … Read more
Yes this is most definitely possible as I have done it when creating clients through javax.xml.ws.EndpointReference, a WS-A related class. I have added a classpath reference to the WSDL to the WS-A EndPointReference and the Metro implementation of JAX-WS loaded it just fine. Whether loading the WSDL from the WS-A EndPointReference or from a file … Read more
There’s more to it than that. There is some ambiguity in the standards that can cause interoperability problems. You have to use type or element depending on whether you’re using a Document-based service or an RPC-based service. There are also ambiguities. If you say <wsdl:message name=”message1″ type=”ns:type1″/> Then you’ve said that the content of the … Read more
You can use SoapUI: http://www.soapui.org/ This is a generally handy program. Make a new project, connect to the WSDL link, then right click on the project and say “Show interface viewer”. Under “Schemas” on the left you can see the XSD. SoapUI can do many things though!
By postfixing the URL with ?WSDL If the URL is for example: http://webservice.example:1234/foo You use: http://webservice.example:1234/foo?WSDL And the wsdl will be delivered.
Keep in mind, I’m completely biased (PMC Chair of CXF), but my thoughts: From a strictly “can the project do what I need it to do” perspective, both are pretty equivalent. There some “edge case” things that CXF can do that Axis 2 cannot and vice versa. But for 90% of the use cases, either … Read more