Re: Unreachable code with WSDL2Java
Nicolas-
Can we see the class for WebServiceAncreStub?M-
*This
email message and any files transmitted with it contain
confidentialinformation intended only for the person(s) to whom this email
message isaddressed. If you have received this email message in error,
please notifythe sender immediately by telephone or email and destroy the
originalmessage without making a copy. Thank you.
- Original Message -
From:
Nicolas
Urien
To: axis-user@ws.apache.org
Sent: Monday, July 10, 2006 4:24 AM
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-std-SNAPSHOT-bin.However, my client is now experiencing a new
exception at run-time :( : (Unexpected subelement return)Exception in
thread "main" java.lang.RuntimeException: java.lang.RuntimeException:
Unexpected subelement return at
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:28001)
at
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.countBySiret(WebServiceAncreStub.java:4108)
at fr.acoss.ancre.acces.dao.ws.client.Client.main(Client.java:22)Caused
by: java.lang.RuntimeException: Unexpected subelement
return at
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub$CountBySiretResponse$Factory.parse(WebServiceAncreStub.java:25157)
at
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:27813)
... 2 moreHere is my client code:WebServiceAncreStub stub
= new
WebServiceAncreStub();
//Create the request
WebServiceAncreStub.CountBySiret request = new
WebServiceAncreStub.CountBySiret();
request.setParam0("17080431400149");
//Invoke the service // THIS IS THE LINE
causing the problem
CountBySiretResponse response =
stub.countBySiret(request);
//System.out.println("Response : " + response.get_return());What
can I do please? (I have already googled for it but returned 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
AMSubject: Re: Unreachable code with WSDL2Java
The Axis1 client will execute as before; the Axis2 service will be
faster.Whether you perceive a difference depends on where you experience
theperformance bottleneck.AnneOn 7/5/06, Nicolas Urien
<[EMAIL PROTECTED]> wrote:>>> Thanks Anne,
this is more clear for me now.>> So I am in the
situation where my Axis1 client talks to an Axis2 service.>> So
my next question is> :> - In this specific situation, do I loose
Axis2 performance advantages> compared to Axis1?Is it the same on the
client (axis1 client) and server> side (Axis2 service
side)?>> I really appreciate your help,>>>
- Original 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 Java2WSDL tool to generate a WSDL for>
Axis2.>> The same is not true of a WSDL2Java tool. These tools
are tied to a> specific SOAP stack. So if you use the Axis1 WSDL2Java
tool to> generate a client stub, then the client must use the Axis1
runtime.> Likewise, if you use the Axis2 WSDL2Java tool to generate a
client> stub, then the client must use the Axis2
runtime.>> But SOAP stacks are interoperable. So you can use an
Axis1 client to> talk to an Axis2 service.>> Hope that's
clear.>> Anne>> On 7/5/06, Nicolas Urien
<[EMAIL PROTECTED]> wrote:> >> >> >
Hi Anne,> >> > Just to be sure we understand each
other.> >> >> > "You cannot use the Axis1
WSDL2Java tool to generate an Axis2 service."> >> > Right
now, I have deployed an axis2 AAR archive file (automatic 1.0 build>
> generation of axis2).> > Now my problem is to have correct
generated stubs for the client (a> separate> > java
application) of this AAR axis2 web service.> >> > I could
generate these client stubs by using Axis1 WSDL2Java tool but not> >
Axis2 WSDL2Java. Then my client can invoke and receive operations fine>
from> > mu AAR axis2 web service.> >&g
Re: Unreachable code with WSDL2Java
Nicolas,
I think this comes from problem about RPCMessageReceiver.
Because of "return" is NOT qualified well.
http://issues.apache.org/jira/browse/AXIS2-865
Regards,
kinichiro
--- Nicolas Urien <[EMAIL PROTECTED]> wrote:
> 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-std-SNAPSHOT-bin.
>
> However, my client is now experiencing a new exception at run-time :(
> : (Unexpected subelement return)
>
> Exception in thread "main" java.lang.RuntimeException:
> java.lang.RuntimeException: Unexpected subelement return
> at
>
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:28001)
> at
>
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.countBySiret(WebServiceAncreStub.java:4108)
> at fr.acoss.ancre.acces.dao.ws.client.Client.main(Client.java:22)
> Caused by: java.lang.RuntimeException: Unexpected subelement return
> at
>
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub$CountBySiretResponse$Factory.parse(WebServiceAncreStub.java:25157)
> at
>
fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:27813)
> ... 2 more
>
>
> Here is my client code:
>
> WebServiceAncreStub stub = new WebServiceAncreStub();
>
> //Create the request
> WebServiceAncreStub.CountBySiret request = new
> WebServiceAncreStub.CountBySiret();
> request.setParam0("17080431400149");
>
> //Invoke the service
> // THIS IS THE LINE causing the problem
> CountBySiretResponse response = stub.countBySiret(request);
>
> //System.out.println("Response : " + response.get_return());
>
>
> What can I do please? (I have already googled for it but returned
> 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 as before; the Axis2 service will be
> faster.
> Whether you perceive a difference depends on where you experience the
> performance bottleneck.
>
> Anne
>
> On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:
> >
> >
> > Thanks Anne, this is more clear for me now.
> >
> > So I am in the situation where my Axis1 client talks to an Axis2
> service.
> >
> > So my next question is
> > :
> > - In this specific situation, do I loose Axis2 performance
> advantages
> > compared to Axis1?Is it the same on the client (axis1 client) and
> server
> > side (Axis2 service side)?
> >
> > I really appreciate your help,
> >
> >
> > - Original 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 Java2WSDL tool to generate a WSDL for
> > Axis2.
> >
> > The same is not true of a WSDL2Java tool. These tools are tied to a
> > specific SOAP stack. So if you use the Axis1 WSDL2Java tool to
> > generate a client stub, then the client must use the Axis1 runtime.
> > Likewise, if you use the Axis2 WSDL2Java tool to generate a client
> > stub, then the client must use the Axis2 runtime.
> >
> > But SOAP stacks are interoperable. So you can use an Axis1 client
> to
> > talk to an Axis2 service.
> >
> > Hope that's clear.
> >
> > Anne
> >
> > On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Hi Anne,
> > >
> > > Just to be sure we understand each other.
> > >
> > >
> > > "You cannot use the Axis1 WSDL2Java tool to generate an Axis2
> service."
> > >
> > > Right now, I have deployed an axis2 AAR archive file (automatic
> 1.0 build
> > > generation of axis2).
> > > Now my problem is to have correct generated stubs for the client
> (a
> > separate
> > > java application) of this AAR axis2 web service.
> > >
> > > I could generate these client stubs by using Axis1 WSDL2Java tool
> but not
> > > Axis2 WSDL2Java. Then my client can
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-std-SNAPSHOT-bin.However, my client is now experiencing a new exception at run-time :( : (Unexpected subelement return)Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement return at fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:28001) at fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.countBySiret(WebServiceAncreStub.java:4108) at
fr.acoss.ancre.acces.dao.ws.client.Client.main(Client.java:22)Caused by: java.lang.RuntimeException: Unexpected subelement return at fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub$CountBySiretResponse$Factory.parse(WebServiceAncreStub.java:25157) at fr.acoss.ancre.acces.dao.ws.WebServiceAncreStub.fromOM(WebServiceAncreStub.java:27813) ... 2 moreHere is my client code:WebServiceAncreStub stub = new WebServiceAncreStub(); //Create the request WebServiceAncreStub.CountBySiret request = new WebServiceAncreStub.CountBySiret(); request.setParam0("17080431400149"); //Invoke the service // THIS IS THE LINE causing the
problem CountBySiretResponse response = stub.countBySiret(request); //System.out.println("Response : " + response.get_return());What can I do please? (I have already googled for it but returned 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 AMSubject: Re: Unreachable code with WSDL2JavaThe Axis1 client will execute as before; the Axis2 service will be faster.Whether you perceive a difference depends on where you experience theperformance bottleneck.AnneOn 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>>
Thanks Anne, this is more clear for me now.>> So I am in the situation where my Axis1 client talks to an Axis2 service.>> So my next question is> :> - In this specific situation, do I loose Axis2 performance advantages> compared to Axis1?Is it the same on the client (axis1 client) and server> side (Axis2 service side)?>> I really appreciate your help,>>> - Original 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 Java2WSDL tool to generate a WSDL for> Axis2.>> The same is not true of a WSDL2Java tool. These tools are
tied to a> specific SOAP stack. So if you use the Axis1 WSDL2Java tool to> generate a client stub, then the client must use the Axis1 runtime.> Likewise, if you use the Axis2 WSDL2Java tool to generate a client> stub, then the client must use the Axis2 runtime.>> But SOAP stacks are interoperable. So you can use an Axis1 client to> talk to an Axis2 service.>> Hope that's clear.>> Anne>> On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:> >> >> > Hi Anne,> >> > Just to be sure we understand each other.> >> >> > "You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service."> >> > Right now, I have deployed an axis2 AAR archive file (automatic 1.0 build> > generation of axis2).> > Now my problem is to have correct generated stubs for the client
(a> separate> > java application) of this AAR axis2 web service.> >> > I could generate these client stubs by using Axis1 WSDL2Java tool but not> > Axis2 WSDL2Java. Then my client can invoke and receive operations fine> from> > mu AAR axis2 web service.> >> > Is there still anything wrong?> >> > 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 strongly> > suggest that you upgrade to the latest nightly build. The 1.0 build> > has lot of WSDL generation
bugs.> >> > Alternatively, you can use the Axis1 Java2WSDL tool to generate a> > WSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp.> >> > You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service.> >> > Anne> &
Re: Unreachable code with WSDL2Java
The Axis1 client will execute as before; the Axis2 service will be faster. Whether you perceive a difference depends on where you experience the performance bottleneck. Anne On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: Thanks Anne, this is more clear for me now. So I am in the situation where my Axis1 client talks to an Axis2 service. So my next question is : - In this specific situation, do I loose Axis2 performance advantages compared to Axis1?Is it the same on the client (axis1 client) and server side (Axis2 service side)? I really appreciate your help, - Original 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 Java2WSDL tool to generate a WSDL for Axis2. The same is not true of a WSDL2Java tool. These tools are tied to a specific SOAP stack. So if you use the Axis1 WSDL2Java tool to generate a client stub, then the client must use the Axis1 runtime. Likewise, if you use the Axis2 WSDL2Java tool to generate a client stub, then the client must use the Axis2 runtime. But SOAP stacks are interoperable. So you can use an Axis1 client to talk to an Axis2 service. Hope that's clear. Anne On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: > > > Hi Anne, > > Just to be sure we understand each other. > > > "You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service." > > Right now, I have deployed an axis2 AAR archive file (automatic 1.0 build > generation of axis2). > Now my problem is to have correct generated stubs for the client (a separate > java application) of this AAR axis2 web service. > > I could generate these client stubs by using Axis1 WSDL2Java tool but not > Axis2 WSDL2Java. Then my client can invoke and receive operations fine from > mu AAR axis2 web service. > > Is there still anything wrong? > > 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 strongly > suggest that you upgrade to the latest nightly build. The 1.0 build > has lot of WSDL generation bugs. > > Alternatively, you can use the Axis1 Java2WSDL tool to generate a > WSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp. > > You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service. > > Anne > > On 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: > > > > > > 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 still benefit of all axis2 features, especially regarding > performance > > (on both server and client side)? > > > > - isn't there a way to make this WSDL2Java tool from Axis2 work? > > > > > > Thanks a million for your help and knowledge, > > > > > > > > - Original Message > > From: Anne Thomas Manes <[EMAIL PROTECTED]> > > To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]> > > Sent: Tuesday, July 4, 2006 6:04:08 PM > > Subject: Re: Unreachable code with WSDL2Java > > > > > > 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 it would be an issue with my WSDL file (my aar archive is > > > WebServiceAncre.aar) : > > > > > > Thanks for help. > > > > > > > > > > > > - > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" > > > xmlns:axis2="http://ws.apache.org/axis2" > > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" > > > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" > > &
Re: Unreachable code with WSDL2Java
Thanks Anne, this is more clear for me now.So I am in the situation where my Axis1 client talks to an Axis2 service.So my next question is:- In this specific situation, do I loose Axis2 performance advantages compared to Axis1?Is it the same on the client (axis1 client) and server side (Axis2 service side)?I really appreciate your help,- Original 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 PMSubject: Re: Unreachable code with WSDL2JavaJust to clarify -- a Java2WSDL tool is independent of any SOAP stack.So you could use the Axis1 Java2WSDL tool to generate a WSDL forAxis2.The same is not true of a WSDL2Java tool. These tools are tied to aspecific SOAP stack. So if you use the Axis1 WSDL2Java tool togenerate a client stub, then the client must use the Axis1 runtime.Likewise, if you use the Axis2 WSDL2Java tool to generate a clientstub, then the client must use the Axis2 runtime.But SOAP stacks are interoperable. So you can use an Axis1 client totalk to an Axis2 service.Hope that's clear.AnneOn 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> Hi Anne,>> Just to be sure we understand each other.>>> "You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service.">> Right now, I have deployed an axis2 AAR archive file (automatic 1.0 build> generation of axis2).> Now my problem is to have correct generated stubs for the client (a separate> java application) of this AAR axis2 web service.>> I could generate these client stubs by using Axis1 WSDL2Java tool but not> Axis2 WSDL2Java. Then my client can invoke and receive operations fine from> mu AAR axis2 web service.>> Is there still anything wrong?>> 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 strongly> suggest that you upgrade to the latest nightly build. The 1.0 build> has lot of WSDL generation bugs.>> Alternatively, you can use the Axis1 Java2WSDL tool to generate a> WSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp.>> You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service.>> Anne>> On 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:> >> >> > 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 still benefit of all axis2 features, especially regarding> performance> > (on both server and client side)?> >> > - isn't there a way to make this WSDL2Java tool from Axis2 work?> >> >> > Thanks a million for your help and knowledge,> >> >> >> > - Original Message > > From: Anne Thomas Manes <[EMAIL PROTECTED]>> > To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>> > Sent: Tuesday, July 4, 2006 6:04:08 PM> > Subject: Re: Unreachable code with WSDL2Java> >> >> > 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 it would be an issue with my WSDL file (my aar archive is> > > WebServiceAncre.aar) :> > >> > > Thanks for help.> > >> > >> > >> > > - > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> > > xmlns:axis2="http://ws.apache.org/axis2"> > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"> > > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"> > >> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"> > > xmln
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 tools are tied to a specific SOAP stack. So if you use the Axis1 WSDL2Java tool to generate a client stub, then the client must use the Axis1 runtime. Likewise, if you use the Axis2 WSDL2Java tool to generate a client stub, then the client must use the Axis2 runtime. But SOAP stacks are interoperable. So you can use an Axis1 client to talk to an Axis2 service. Hope that's clear. Anne On 7/5/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: Hi Anne, Just to be sure we understand each other. "You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service." Right now, I have deployed an axis2 AAR archive file (automatic 1.0 build generation of axis2). Now my problem is to have correct generated stubs for the client (a separate java application) of this AAR axis2 web service. I could generate these client stubs by using Axis1 WSDL2Java tool but not Axis2 WSDL2Java. Then my client can invoke and receive operations fine from mu AAR axis2 web service. Is there still anything wrong? 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 strongly suggest that you upgrade to the latest nightly build. The 1.0 build has lot of WSDL generation bugs. Alternatively, you can use the Axis1 Java2WSDL tool to generate a WSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp. You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service. Anne On 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: > > > 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 still benefit of all axis2 features, especially regarding performance > (on both server and client side)? > > - isn't there a way to make this WSDL2Java tool from Axis2 work? > > > Thanks a million for your help and knowledge, > > > > - Original Message > From: Anne Thomas Manes <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]> > Sent: Tuesday, July 4, 2006 6:04:08 PM > Subject: Re: Unreachable code with WSDL2Java > > > 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 it would be an issue with my WSDL file (my aar archive is > > WebServiceAncre.aar) : > > > > Thanks for help. > > > > > > > > - > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" > > xmlns:axis2="http://ws.apache.org/axis2" > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" > > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" > > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" > > xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd" > > xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd" > > xmlns:ns3="http://util.java/xsd" xmlns:ns2="http://sql.java/xsd" > > xmlns:xs="http://www.w3.org/2001/XMLSchema" > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > > targetNamespace="http://ws.apache.org/axis2"> > > > > > > - > > > > > > - http://sql.java/xsd" > > xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd" > > > targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd" > > elementFormDefault="unqualified" > attributeFormDefault="unqualified"> > > > > > > http://sql.java/xsd" /> > > > > > > > > - > > > > > > - > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Unreachable code with WSDL2Java
Hi Anne,Just to be sure we understand each other."You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service."Right now, I have deployed an axis2 AAR archive file (automatic 1.0 build generation of axis2).Now my problem is to have correct generated stubs for the client (a separate java application) of this AAR axis2 web service.I could generate these client stubs by using Axis1 WSDL2Java tool but not Axis2 WSDL2Java. Then my client can invoke and receive operations fine from mu AAR axis2 web service.Is there still anything wrong?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 PMSubject: Re: Unreachable code with WSDL2JavaIf you want Axis2 to generate your WSDL for you, then I stronglysuggest that you upgrade to the latest nightly build. The 1.0 buildhas lot of WSDL generation bugs.Alternatively, you can use the Axis1 Java2WSDL tool to generate aWSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp.You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service.AnneOn 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> 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 still benefit of all axis2 features, especially regarding performance> (on both server and client side)?>> - isn't there a way to make this WSDL2Java tool from Axis2 work?>>> Thanks a million for your help and knowledge,>>>> - Original Message > From: Anne Thomas Manes <[EMAIL PROTECTED]>> To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>> Sent: Tuesday, July 4, 2006 6:04:08 PM> Subject: Re: Unreachable code with WSDL2Java>>> 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 it would be an issue with my WSDL file (my aar archive is> > WebServiceAncre.aar) :> >> > Thanks for help.> >> >> >> > - > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";;> > xmlns:axis2="http://ws.apache.org/axis2";;> > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";;> > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";;> > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";;> > xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd";;> > xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd";;> > xmlns:ns3="http://util.java/xsd";; xmlns:ns2="http://sql.java/xsd";;> > xmlns:xs="http://www.w3.org/2001/XMLSchema";;> > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";;> > targetNamespace="http://ws.apache.org/axis2";;>> >> >> > - > >> >> > - http://sql.java/xsd";;> > xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd";;> >> targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd";;> > elementFormDefault="unqualified"> attributeFormDefault="unqualified">> >> >> > http://sql.java/xsd";; />> >> > > >> > - > >> >> > - > >> >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > name="addresseCompte" />> >> > > name="addresseSiretCompte"> > />> > > > > >> > > > name="AdresseCompteAncreBean" />> >> > - > >> >> > - > >&g
Re: Unreachable code with WSDL2Java
If you want Axis2 to generate your WSDL for you, then I strongly suggest that you upgrade to the latest nightly build. The 1.0 build has lot of WSDL generation bugs. Alternatively, you can use the Axis1 Java2WSDL tool to generate a WSDL; then use the Axis2 WSDL2Java tool to generate your Axis2 webapp. You cannot use the Axis1 WSDL2Java tool to generate an Axis2 service. Anne On 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote: 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 still benefit of all axis2 features, especially regarding performance (on both server and client side)? - isn't there a way to make this WSDL2Java tool from Axis2 work? Thanks a million for your help and knowledge, - Original Message From: Anne Thomas Manes <[EMAIL PROTECTED]> To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]> Sent: Tuesday, July 4, 2006 6:04:08 PM Subject: Re: Unreachable code with WSDL2Java 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 it would be an issue with my WSDL file (my aar archive is > WebServiceAncre.aar) : > > Thanks for help. > > > > - xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";; > xmlns:axis2="http://ws.apache.org/axis2";; > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";; > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";; > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";; > xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd";; > xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd";; > xmlns:ns3="http://util.java/xsd";; xmlns:ns2="http://sql.java/xsd";; > xmlns:xs="http://www.w3.org/2001/XMLSchema";; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";; > targetNamespace="http://ws.apache.org/axis2";;> > > > - > > > - http://sql.java/xsd";; > xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd";; > targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd";; > elementFormDefault="unqualified" attributeFormDefault="unqualified"> > > > http://sql.java/xsd";; /> > > > > - > > > - > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >/> > > > >name="AdresseCompteAncreBean" /> > > - > > > - > > > > > > > > > > > > > > > > > > > > > > > > - http://util.java/xsd";; > xmlns:ns="http://ws.dao.acces.ancre.acoss.fr/xsd";; > xmlns:stn_7="http://bean.dao.acces.ancre.acoss.fr/xsd";; > targetNamespace="http://ws.dao.acces.ancre.acoss.fr/xsd";; > elementFormDefault="unqualified" attributeFormDefault="unqualified"> > > > http://util.java/xsd";; /> > >namespace="http://bean.dao.acces.ancre.acoss.fr/xsd";; /> > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - name="countByNumCpteInterneAndNumOrgaResponse"> > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - > > > - > > > - > > > > > > > > - > > > - > > > - > > > > > > > > > > - > > > - > > > - > > > > > > > > - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unreachable code with WSDL2Java
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 still benefit of all axis2 features, especially regarding performance (on both server and client side)?- isn't there a way to make this WSDL2Java tool from Axis2 work?Thanks a million for your help and knowledge,- Original Message From: Anne Thomas Manes <[EMAIL PROTECTED]>To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>Sent: Tuesday, July 4, 2006 6:04:08 PMSubject: Re: Unreachable code with WSDL2JavaYour 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 theJava2WSDL tool from Axis1 (assuming that you want just a SOAP 1.1binding).AnneOn 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> Hi,>> Just in case it would be an issue with my WSDL file (my aar archive is> WebServiceAncre.aar) :>> Thanks for help. - > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> xmlns:axis2="http://ws.apache.org/axis2";> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";> xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd";> xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd";> xmlns:ns3="http://util.java/xsd"; xmlns:ns2="http://sql.java/xsd";> xmlns:xs="http://www.w3.org/2001/XMLSchema";> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> targetNamespace="http://ws.apache.org/axis2"; - >>> - http://sql.java/xsd";> xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd";> targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd";> elementFormDefault="unqualified" attributeFormDefault="unqualified" http://sql.java/xsd"; />>> >> - >>> - >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > />> > >> > name="AdresseCompteAncreBean" />>> - >>> - >>> >> >> >> >> >> >> >> >> > > > >> - http://util.java/xsd";> xmlns:ns="http://ws.dao.acces.ancre.acoss.fr/xsd";> xmlns:stn_7="http://bean.dao.acces.ancre.acoss.fr/xsd";> targetNamespace="http://ws.dao.acces.ancre.acoss.fr/xsd";> elementFormDefault="unqualified" attributeFormDefault="unqualified" http://util.java/xsd"; />>> > namespace="http://bean.dao.acces.ancre.acoss.fr/xsd"; />>> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - > name="countByNumCpteInterneAndNumOrgaResponse" - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> -
Re: Unreachable code with WSDL2Java
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, especially regarding performance (on both server and client side)?- isn't there a way to make this Java2WSDL tool from Axis2 work?Thanks a million for your help and knowledge,- Original Message From: Anne Thomas Manes <[EMAIL PROTECTED]>To: axis-user@ws.apache.org; Nicolas Urien <[EMAIL PROTECTED]>Sent: Tuesday, July 4, 2006 6:04:08 PMSubject: Re: Unreachable code with WSDL2JavaYour 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 theJava2WSDL tool from Axis1 (assuming that you want just a SOAP 1.1binding).AnneOn 7/4/06, Nicolas Urien <[EMAIL PROTECTED]> wrote:>>> Hi,>> Just in case it would be an issue with my WSDL file (my aar archive is> WebServiceAncre.aar) :>> Thanks for help. - > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> xmlns:axis2="http://ws.apache.org/axis2";> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";> xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd";> xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd";> xmlns:ns3="http://util.java/xsd"; xmlns:ns2="http://sql.java/xsd";> xmlns:xs="http://www.w3.org/2001/XMLSchema";> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> targetNamespace="http://ws.apache.org/axis2"; - >>> - http://sql.java/xsd";> xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd";> targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd";> elementFormDefault="unqualified" attributeFormDefault="unqualified" http://sql.java/xsd"; />>> >> - >>> - >>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > />> > >> > name="AdresseCompteAncreBean" />>> - >>> - >>> >> >> >> >> >> >> >> >> > > > >> - http://util.java/xsd";> xmlns:ns="http://ws.dao.acces.ancre.acoss.fr/xsd";> xmlns:stn_7="http://bean.dao.acces.ancre.acoss.fr/xsd";> targetNamespace="http://ws.dao.acces.ancre.acoss.fr/xsd";> elementFormDefault="unqualified" attributeFormDefault="unqualified" http://util.java/xsd"; />>> > namespace="http://bean.dao.acces.ancre.acoss.fr/xsd"; />>> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - > name="countByNumCpteInterneAndNumOrgaResponse" - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> - >>> - >>> - >>> >> > > > >> - >>> - >>> - >>> > > > >> -
Re: Unreachable code with WSDL2Java
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 it would be an issue with my WSDL file (my aar archive is WebServiceAncre.aar) : Thanks for help. - http://schemas.xmlsoap.org/wsdl/"; xmlns:axis2="http://ws.apache.org/axis2"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; xmlns:ns0="http://bean.dao.acces.ancre.acoss.fr/xsd"; xmlns:ns1="http://ws.dao.acces.ancre.acoss.fr/xsd"; xmlns:ns3="http://util.java/xsd"; xmlns:ns2="http://sql.java/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; targetNamespace="http://ws.apache.org/axis2";> - - http://sql.java/xsd"; xmlns:stn_2="http://bean.dao.acces.ancre.acoss.fr/xsd"; targetNamespace="http://bean.dao.acces.ancre.acoss.fr/xsd"; elementFormDefault="unqualified" attributeFormDefault="unqualified"> http://sql.java/xsd"; /> - - - - - http://util.java/xsd"; xmlns:ns="http://ws.dao.acces.ancre.acoss.fr/xsd"; xmlns:stn_7="http://bean.dao.acces.ancre.acoss.fr/xsd"; targetNamespace="http://ws.dao.acces.ancre.acoss.fr/xsd"; elementFormDefault="unqualified" attributeFormDefault="unqualified"> http://util.java/xsd"; /> http://bean.dao.acces.ancre.acoss.fr/xsd"; /> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unreachable code with WSDL2Java
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 :// create SOAP envelope with that payloadorg.apache.axiom.soap.SOAPEnvelope env = null;Please help me! I feel desperate about thisThnaks- Original Message From: Nicolas Urien <[EMAIL PROTECTED]>To: axis-user@ws.apache.orgSent: Tuesday, July 4, 2006 11:55:57 AMSubject: Unreachable code with
WSDL2JavaHi,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 org.apache.axis2.context.MessageContext() ;Here is the command I launched:WSDL2Java.bat -uri http://localhost:8080/axis2/services/WebServiceAncre?wsdl -p fr.acoss.ancre.acces.dao.ws -o .I have tried both 1.0 release + nightly. My web service has only one port.Help will be GREATLY appreciated. Thank you a million in advance (this is critical for
me).
