Re: port name and binding name overwriting
can you send your wsdl or a sample wsdl to show the problem? Amila. On 11/5/07, ROBINSON JULIEN <[EMAIL PROTECTED]> wrote: > > > Hi all, > > I'm generating code from a WSDL using > org.apache.axis2.tool.ant.AntCodegenTask > > In my WSDL, the service definition looks like this: > > > Blabla > >location="http://localhost:8080/jarname/services/some"; /> > > > > Note that the port name and binding name are the same. This works fine > for Axis 1 and JAX-WS RI, but Axis2 generates two classes, one for the > port type (interface describing the port) and one for the binding > (utility for calling an instance). > > Problem is, one of these classes overwrites the other one! So that the > other one, overwritten, is missing in the generated package. > > I have several WSDL files in my project, some are editable but others > are legacy, and I don't want to edit them. Plus, as I said, this works > fine with other tools. > > Is there any way, possibly a bug fix or simply a configuration of the > WSDL2Java (codegen) task, for a workaround? Perhaps to tell it to > generate binding somewhere else? > > Thanks for any tips! > Julien > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc.
RE: port name and binding name overwriting
Here are a pair of WSDL files and an Ant file to generate the Java. Ant libraries (jar files) should be in a directory called axis_lib. My current version is Axis2 1.3 (downloaded 13/09/2007). Reminder: the issue is when port and binding have the same name, generated Java files are overwritten. Note that the same WSDL files have been tested with Axis (1.2) and JAX-WS RI and work fine in both cases. In fact these WSDLs have been derived from production ones. * Results from the "diff" version: - port and binding have different names - The generated code doesn't compile. I don't know why. I'd say it is a distinct problem. Any idea to make it compile? - There are two stubs: * BuzzerSoapBindingStub, which may be used by a client to invoke the service * BuzzerSoapStub, which is the interface of the service * Results from the same version: - in the "same" version, port and binding have the same name. There is a missing class, the binding stub class (for calling the service). Obviously, it seems to have been overwritten by the interface stub. - note that if we use overwrite="true", the overwrite is the other way round: we have the binding stub class, but not the interface! Any help would be appreciated. Julien > -Message d'origine- > De : Amila Suriarachchi [mailto:[EMAIL PROTECTED] > Envoyé : mardi 6 novembre 2007 05:32 > À : axis-user@ws.apache.org > Objet : Re: port name and binding name overwriting > > can you send your wsdl or a sample wsdl to show the problem? > > Amila. > > > On 11/5/07, ROBINSON JULIEN < > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > wrote: > > > Hi all, > > I'm generating code from a WSDL using > org.apache.axis2.tool.ant.AntCodegenTask > > In my WSDL, the service definition looks like this: > > > Blabla >binding="myns:someServiceSoap"> > > location="http://localhost:8080/jarname/services/some " /> > > > > Note that the port name and binding name are the same. > This works fine > for Axis 1 and JAX-WS RI, but Axis2 generates two > classes, one for the > port type (interface describing the port) and one for > the binding > (utility for calling an instance). > > Problem is, one of these classes overwrites the other > one! So that the > other one, overwritten, is missing in the generated package. > > I have several WSDL files in my project, some are > editable but others > are legacy, and I don't want to edit them. Plus, as I > said, this works > fine with other tools. > > Is there any way, possibly a bug fix or simply a > configuration of the > WSDL2Java (codegen) task, for a workaround? Perhaps to > tell it to > generate binding somewhere else? > > Thanks for any tips! > Julien buzzer_diff.wsdl Description: buzzer_diff.wsdl buzzer_same.wsdl Description: buzzer_same.wsdl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: port name and binding name overwriting
On Nov 9, 2007 3:25 PM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > On Nov 9, 2007 3:25 PM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > On Nov 6, 2007 4:20 PM, ROBINSON JULIEN > > <[EMAIL PROTECTED]> wrote: > > > > > > Here are a pair of WSDL files and an Ant file to generate the Java. > > > Ant libraries (jar files) should be in a directory called axis_lib. > > > My current version is Axis2 1.3 (downloaded 13/09/2007). > > > Reminder: the issue is when port and binding have the same name, > > > generated Java files are overwritten. > > > > > > Note that the same WSDL files have been tested with Axis (1.2) and JAX-WS > > > RI and work fine in both cases. In fact these WSDLs have been derived > > > from production ones. > > > > > > * Results from the "diff" version: > > > - port and binding have different names > > > - The generated code doesn't compile. I don't know why. I'd say it is a > > > distinct problem. Any idea to make it compile? > > > - There are two stubs: > > > * BuzzerSoapBindingStub, which may be used by a client to invoke > > > the service > > > * BuzzerSoapStub, which is the interface of the service > > Can you generate the code with wsdl2java tool and see. > > here with I have attached the code generated for diff using these > > options > > -uri buzzer_diff.wsdl -ss -sd -u -g -ssi -uw > > > > can you check with your generated code? > > > > thanks, > > Amila. > > > > > > > > * Results from the same version: > > > - in the "same" version, port and binding have the same name. There is a > > > missing class, the binding stub class (for calling the service). > > > Obviously, it seems to have been overwritten by the interface stub. > > > - note that if we use overwrite="true", the overwrite is the other way > > > round: we have the binding stub class, but not the interface! > > > > > > Any help would be appreciated. > > > Julien > > > > > > > -Message d'origine- > > > > De : Amila Suriarachchi [mailto:[EMAIL PROTECTED] > > > > Envoyé : mardi 6 novembre 2007 05:32 > > > > À : axis-user@ws.apache.org > > > > Objet : Re: port name and binding name overwriting > > > > > > > > can you send your wsdl or a sample wsdl to show the problem? > > > > > > > > Amila. > > > > > > > > > > > > On 11/5/07, ROBINSON JULIEN < > > > > [EMAIL PROTECTED] > > > > > > > <mailto:[EMAIL PROTECTED]> > wrote: > > > > > > > > > > > > Hi all, > > > > > > > > I'm generating code from a WSDL using > > > > org.apache.axis2.tool.ant.AntCodegenTask > > > > > > > > In my WSDL, the service definition looks like this: > > > > > > > > > > > > Blabla > > > >> > > binding="myns:someServiceSoap"> > > > > > > > > > > > location="http://localhost:8080/jarname/services/some " /> > > > > > > > > > > > > > > > > Note that the port name and binding name are the same. > > > > This works fine > > > > for Axis 1 and JAX-WS RI, but Axis2 generates two > > > > classes, one for the > > > > port type (interface describing the port) and one for > > > > the binding > > > > (utility for calling an instance). > > > > > > > > Problem is, one of these classes overwrites the other > > > > one! So that the > > > > other one, overwritten, is missing in the generated package. > > > > > > > > I have several WSDL files in my project, some are > > > > editable but others > > > > are legacy, and I don't want to edit them. Plus, as I > > > > said, this works > > > > fine with other tools. > > > > > > > > Is there any way, possibly a bug fix or simply a > > > > configuration of the > > > > WSDL2Java (codegen) task, for a workaround? Perhaps to > > > > tell it to > > > > generate binding somewhere else? > > > > > > > > Thanks for any tips! > > > > Julien > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > -- > > Amila Suriarachchi, > > WSO2 Inc. > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. > -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: port name and binding name overwriting
On Nov 6, 2007 4:20 PM, ROBINSON JULIEN <[EMAIL PROTECTED]> wrote: > > Here are a pair of WSDL files and an Ant file to generate the Java. > Ant libraries (jar files) should be in a directory called axis_lib. > My current version is Axis2 1.3 (downloaded 13/09/2007). > Reminder: the issue is when port and binding have the same name, generated > Java files are overwritten. > > Note that the same WSDL files have been tested with Axis (1.2) and JAX-WS RI > and work fine in both cases. In fact these WSDLs have been derived from > production ones. > > * Results from the "diff" version: > - port and binding have different names > - The generated code doesn't compile. I don't know why. I'd say it is a > distinct problem. Any idea to make it compile? > - There are two stubs: > * BuzzerSoapBindingStub, which may be used by a client to invoke the > service > * BuzzerSoapStub, which is the interface of the service Can you generate the code with wsdl2java tool and see. here with I have attached the code generated for diff using these options -uri buzzer_diff.wsdl -ss -sd -u -g -ssi -uw can you check with your generated code? thanks, Amila. > > * Results from the same version: > - in the "same" version, port and binding have the same name. There is a > missing class, the binding stub class (for calling the service). Obviously, > it seems to have been overwritten by the interface stub. > - note that if we use overwrite="true", the overwrite is the other way round: > we have the binding stub class, but not the interface! > > Any help would be appreciated. > Julien > > > -Message d'origine----- > > De : Amila Suriarachchi [mailto:[EMAIL PROTECTED] > > Envoyé : mardi 6 novembre 2007 05:32 > > À : axis-user@ws.apache.org > > Objet : Re: port name and binding name overwriting > > > > can you send your wsdl or a sample wsdl to show the problem? > > > > Amila. > > > > > > On 11/5/07, ROBINSON JULIEN < > > [EMAIL PROTECTED] > > > <mailto:[EMAIL PROTECTED]> > wrote: > > > > > > Hi all, > > > > I'm generating code from a WSDL using > > org.apache.axis2.tool.ant.AntCodegenTask > > > > In my WSDL, the service definition looks like this: > > > > > > Blabla > >> binding="myns:someServiceSoap"> > > > > > location="http://localhost:8080/jarname/services/some " /> > > > > > > > > Note that the port name and binding name are the same. > > This works fine > > for Axis 1 and JAX-WS RI, but Axis2 generates two > > classes, one for the > > port type (interface describing the port) and one for > > the binding > > (utility for calling an instance). > > > > Problem is, one of these classes overwrites the other > > one! So that the > > other one, overwritten, is missing in the generated package. > > > > I have several WSDL files in my project, some are > > editable but others > > are legacy, and I don't want to edit them. Plus, as I > > said, this works > > fine with other tools. > > > > Is there any way, possibly a bug fix or simply a > > configuration of the > > WSDL2Java (codegen) task, for a workaround? Perhaps to > > tell it to > > generate binding somewhere else? > > > > Thanks for any tips! > > Julien > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: port name and binding name overwriting
On Nov 9, 2007 3:25 PM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > On Nov 6, 2007 4:20 PM, ROBINSON JULIEN > <[EMAIL PROTECTED]> wrote: > > > > Here are a pair of WSDL files and an Ant file to generate the Java. > > Ant libraries (jar files) should be in a directory called axis_lib. > > My current version is Axis2 1.3 (downloaded 13/09/2007). > > Reminder: the issue is when port and binding have the same name, generated > > Java files are overwritten. > > > > Note that the same WSDL files have been tested with Axis (1.2) and JAX-WS > > RI and work fine in both cases. In fact these WSDLs have been derived from > > production ones. > > > > * Results from the "diff" version: > > - port and binding have different names > > - The generated code doesn't compile. I don't know why. I'd say it is a > > distinct problem. Any idea to make it compile? > > - There are two stubs: > > * BuzzerSoapBindingStub, which may be used by a client to invoke > > the service > > * BuzzerSoapStub, which is the interface of the service > Can you generate the code with wsdl2java tool and see. > here with I have attached the code generated for diff using these > options > -uri buzzer_diff.wsdl -ss -sd -u -g -ssi -uw > > can you check with your generated code? > > thanks, > Amila. > > > > > * Results from the same version: > > - in the "same" version, port and binding have the same name. There is a > > missing class, the binding stub class (for calling the service). Obviously, > > it seems to have been overwritten by the interface stub. > > - note that if we use overwrite="true", the overwrite is the other way > > round: we have the binding stub class, but not the interface! > > > > Any help would be appreciated. > > Julien > > > > > -Message d'origine- > > > De : Amila Suriarachchi [mailto:[EMAIL PROTECTED] > > > Envoyé : mardi 6 novembre 2007 05:32 > > > À : axis-user@ws.apache.org > > > Objet : Re: port name and binding name overwriting > > > > > > can you send your wsdl or a sample wsdl to show the problem? > > > > > > Amila. > > > > > > > > > On 11/5/07, ROBINSON JULIEN < > > > [EMAIL PROTECTED] > > > > > <mailto:[EMAIL PROTECTED]> > wrote: > > > > > > > > > Hi all, > > > > > > I'm generating code from a WSDL using > > > org.apache.axis2.tool.ant.AntCodegenTask > > > > > > In my WSDL, the service definition looks like this: > > > > > > > > > Blabla > > >> > binding="myns:someServiceSoap"> > > > > > > > > location="http://localhost:8080/jarname/services/some " /> > > > > > > > > > > > > Note that the port name and binding name are the same. > > > This works fine > > > for Axis 1 and JAX-WS RI, but Axis2 generates two > > > classes, one for the > > > port type (interface describing the port) and one for > > > the binding > > > (utility for calling an instance). > > > > > > Problem is, one of these classes overwrites the other > > > one! So that the > > > other one, overwritten, is missing in the generated package. > > > > > > I have several WSDL files in my project, some are > > > editable but others > > > are legacy, and I don't want to edit them. Plus, as I > > > said, this works > > > fine with other tools. > > > > > > Is there any way, possibly a bug fix or simply a > > > configuration of the > > > WSDL2Java (codegen) task, for a workaround? Perhaps to > > > tell it to > > > generate binding somewhere else? > > > > > > Thanks for any tips! > > > Julien > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. > -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: port name and binding name overwriting
> > * Results from the "diff" version: > > - port and binding have different names > > - The generated code doesn't compile. I don't know why. I'd > say it is a distinct problem. Any idea to make it compile? > > - There are two stubs: > > * BuzzerSoapBindingStub, which may be used by a > client to invoke the service > > * BuzzerSoapStub, which is the interface of the service > > Can you generate the code with wsdl2java tool and see. > here with I have attached the code generated for diff using these > options > -uri buzzer_diff.wsdl -ss -sd -u -g -ssi -uw > > can you check with your generated code? I've compared, what you sent is nothing like my generated code. Can you tell me how you generate code? What class do you use? For the moment, I was doing this way: java2wsdl: org.apache.ws.java2wsdl.Java2WSDL wsdl2java: org.apache.axis2.tool.ant.AntCodegenTask Note that I generally prefer Ant tasks whenever possible. For Java2wsdl I use the class because the Ant task org.apache.ws.java2wsdl.Java2WSDLTask does not work. Julien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: port name and binding name overwriting
On Nov 9, 2007 5:33 PM, ROBINSON JULIEN <[EMAIL PROTECTED]> wrote: > > > > * Results from the "diff" version: > > > - port and binding have different names > > > - The generated code doesn't compile. I don't know why. I'd > > say it is a distinct problem. Any idea to make it compile? > > > - There are two stubs: > > > * BuzzerSoapBindingStub, which may be used by a > > client to invoke the service > > > * BuzzerSoapStub, which is the interface of the service > > > > Can you generate the code with wsdl2java tool and see. > > here with I have attached the code generated for diff using these > > options > > -uri buzzer_diff.wsdl -ss -sd -u -g -ssi -uw > > > > can you check with your generated code? > > I've compared, what you sent is nothing like my generated code. > > Can you tell me how you generate code? What class do you use? > > For the moment, I was doing this way: > java2wsdl: org.apache.ws.java2wsdl.Java2WSDL > wsdl2java: org.apache.axis2.tool.ant.AntCodegenTask Are you using axis1.x or axis2? I have used axis2. try to do this, dowonload an axis2-SNAPSHOT then extract it and set the AXIS2_HOME correctly then use the wsdl2java tool with the above options. thanks, Amila. > > Note that I generally prefer Ant tasks whenever possible. For Java2wsdl > I use the class because the Ant task > org.apache.ws.java2wsdl.Java2WSDLTask does not work. > > > Julien > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: port name and binding name overwriting
> > For the moment, I was doing this way: > > java2wsdl: org.apache.ws.java2wsdl.Java2WSDL > > wsdl2java: org.apache.axis2.tool.ant.AntCodegenTask > > Are you using axis1.x or axis2? I have used axis2. I am using Axis2. > try to do this, > dowonload an axis2-SNAPSHOT > then extract it and set the AXIS2_HOME correctly > then use the wsdl2java tool with the above options. I'm sure that if I use the same tool as you on the same files, I will get the same result. What class does the wsdl2java tool call? Is it reachable by an Ant task? In fact my question is simple: Please tell me what I should write in my Ant file to do a proper WSDL 2 Java operation. Shouldn't I use codegen? I'm a bit lost in Axis2 because for each operation, wsdl2java and java2wsdl, there seems to be at least 2 solutions... Julien Robinson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: port name and binding name overwriting
On Nov 12, 2007 4:24 PM, ROBINSON JULIEN <[EMAIL PROTECTED]> wrote: > > > > For the moment, I was doing this way: > > > java2wsdl: org.apache.ws.java2wsdl.Java2WSDL > > > wsdl2java: org.apache.axis2.tool.ant.AntCodegenTask > > > > Are you using axis1.x or axis2? I have used axis2. > > I am using Axis2. > > > try to do this, > > dowonload an axis2-SNAPSHOT > > then extract it and set the AXIS2_HOME correctly > > then use the wsdl2java tool with the above options. > interop_server-SNAPSHOT > I'm sure that if I use the same tool as you on the same files, I will > get the same result. > interop_server-SNAPSHOT > What class does the wsdl2java tool call? > Is it reachable by an Ant task? > > In fact my question is simple: Please tell me what I should write in my > Ant file to do a proper WSDL 2 Java operation. > Shouldn't I use codegen? what you have done is correct. check by swith off backworkd compatibility. i.e backwardcompatible="false" - this is the only thing I can assume. if you do what I have asked you to do then we can find the place where you have made the mistake. thanks, Amila. > > I'm a bit lost in Axis2 because for each operation, wsdl2java and > java2wsdl, there seems to be at least 2 solutions... > > Julien Robinson > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: port name and binding name overwriting
> what you have done is correct. check by swith off backworkd > compatibility. > i.e backwardcompatible="false" - this is the only thing I can assume. Wow! Would you believe it, it worked just fine. I assume that backwardcompatible generates SoapStub and stuff like that instead of skeleton etc, in order to conserve Axis1-like naming. Well, it works better with the option off. Thanks a lot, this problem solved! Julien Robinson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
