Urien [EMAIL PROTECTED] Sent: Wednesday, July 5, 2006 3:13:29 PM Subject: Re: Unreachable code with WSDL2Java Just to clarify -- a Java2WSDL tool is independent of any SOAP stack. So you could use the Axis1 Java2WSDL tool to generate a WSDL for Axis2. The same is not true of a WSDL2Java tool. These
articles are very few)
Thanks
- Original Message
From: Anne Thomas Manes [EMAIL PROTECTED]
To: axis-user@ws.apache.org; Nicolas Urien [EMAIL PROTECTED]
Sent: Thursday, July 6, 2006 1:30:12 AM
Subject: Re: Unreachable code with WSDL2Java
The Axis1 client will execute
Subject: Re: Unreachable code with
WSDL2Java
Finally
, the "unreachable code with the axis2 WSDL2Java " has been fixed by using the
latest nightly build AND manually copying axis2-adb-codegen-SNAPSHOT.jar from
the war archive into the lastest nightly
axis2-st
?
thanks for your help,
- Original Message
From: Anne Thomas Manes [EMAIL PROTECTED]
To: axis-user@ws.apache.org; Nicolas Urien [EMAIL PROTECTED]
Sent: Tuesday, July 4, 2006 10:34:53 PM
Subject: Re: Unreachable code with WSDL2Java
If you want Axis2 to generate your WSDL for you, then I
Message
From: Anne Thomas Manes [EMAIL PROTECTED]
To: axis-user@ws.apache.org; Nicolas Urien [EMAIL PROTECTED]
Sent: Wednesday, July 5, 2006 3:13:29 PM
Subject: Re: Unreachable code with WSDL2Java
Just to clarify -- a Java2WSDL tool is independent of any SOAP stack.
So you could use the Axis1
Hi,When I generate my stub with WSDL2java, I got an Unreachable code compilation errors in it.Compilation error is here in my WebServiceAncreStub.java:// create message context with that soap envelopeorg.apache.axis2.context.MessageContext _messageContext = new
Just to narrow the problem a bit more :There are plenty of " //Unsupported style!! No code is generated throw new java.lang.UnsupportedOperationException("Unsupported Style");" generated instructions inside the stub code !These instructions are always generated after SOAP processing like ://
Your WSDL has errors. I assume you generated the WSDL using Java2WSDL.
If you do so, make sure you use the latest build. Or you could use the
Java2WSDL tool from Axis1 (assuming that you want just a SOAP 1.1
binding).
Anne
On 7/4/06, Nicolas Urien [EMAIL PROTECTED] wrote:
Hi,
Just in case
Hi Anne,I didn't use Java2WSDL but instead let the axis2 webapp (release 1.0 as war distribution) on my container generate it automatically.Indeed, I could fix the problem by using Java2WSDL tool from Axis1.I still have those 2 questions though:- do I still benefit of all axis2 features,
Sorry there were mistypes in my previous post.I didn't use Java2WSDL but instead let the axis2 webapp
(release 1.0 as war distribution) on my container generate it
automatically.Indeed, I could fix the problem by using WSDL2Java tool from Axis1.I still have those 2 questions though:- do I
10 matches
Mail list logo