In most of our experiments all of the doc/lit WSDL emitted by Axis 1.2a's
java2WSDL tool was either invalid or not WS-I compliant.
I define "invalid" to mean "not immediately usable for a client to bind to
and successfully invoke the service."
I define "not WS-I compliant" to mean failing Mindreef SOAPScope 2.0's
(recently 3.0) WS-I WSDL compliance checks.
We also ended up defining custom XML schemas for our XML datatypes, and then
importing those schemas into our WSDL to include the datatypes in our WSDL
messages. This was the final decision that ruled out java2WSDL as an option
for us.
If WS-I compliance is not a requirement, and you can live with the Axis XML
datatypes automatically generated and included for you in the emitted WSDL's
type section, I would suggest experimenting with the latest Axis 1.2 CVS.
But it is important to realize that in the "big picture" you are essentially
deciding to either a) model your Java and then work backwards (java2WSDL) to
get your WSDL, or b) model your XML and then work forwards to generate your
Java object model (WSDL2Java).
Regards,
-Jon
-----Original Message-----
From: Saravanan Markandeyan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 5:21 PM
To: '[EMAIL PROTECTED]'
Subject: RE: RPC and Doc/Literal...
Is the hand built WSDL required for this to work. I have a huge interface
that I want to expose
as a service using doc/lit and was wondering, if I picked up 1.2 and used
the JAVA2WSDL and WSDL2JAVA
method, could I get the doc/lit to work. Tried with 1.1 for a while and gave
up.
Has anyone tried the JAVA2WSDL and WSDL2JAVA process to do doc/lit services?
Any input would be
greatly appreciated.
Thanks in advance
-Saravanan
