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
> > > À : [email protected]
> > > 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:
> > >
> > >         <wsdl:service name="someService">
> > >           <wsdl:documentation>Blabla</wsdl:documentation>
> > >           <wsdl:port name="someServiceSoap"
> > > binding="myns:someServiceSoap">
> > >             <soap:address
> > >
> > > location="http://localhost:8080/jarname/services/some " />
> > >           </wsdl:port>
> > >         </wsdl:service>
> > >
> > >       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]

Reply via email to