RE: Java2WSDL - Bug found on generating the wsdl:service Name by java:EJB Provider

[Sascha Kulawik <sa...@kulawik.de>]

Hello,

This problem occures only in Versions after Axis 1.0 on the Serverside.
The WSDL will be generated on the fly through the WSDD with the
"java:EJB" Provider using a Stateless Session Bean.

Regards,

Sascha

> -----Original Message-----
> From: Tom Jordahl [mailto:tomj@macromedia.com] 
> Sent: Monday, December 09, 2002 5:57 PM
> To: 'axis-user@xml.apache.org'
> Subject: RE: WSDL2Java - How to configure the Stubclasses name ?
> 
> 
> 
> The name of your wsdl:service and wsdl:PortType are the same. 
> WSDL2Java resolves the conflict by adding _Service and _Port 
> to the class names.
> 
> Changing the name of your service give you a class name of 
> UnitSession for the PortType.
> 
> Change this:
>   <wsdl:service name="UnitSession">
> To this:
>   <wsdl:service name="UnitSessionService">
> 
> Gives the following output from wsdl2java:
> $ wsdl2java -v UnitSession.wsdl
> Parsing XML file:  UnitSession.wsdl
> [deleted...]
> Generating net\juwimm\conquest\UnitSessionService.java
> Generating net\juwimm\conquest\UnitSessionServiceLocator.java
> Generating net\juwimm\conquest\UnitSession.java
> Generating net\juwimm\conquest\UnitSessionSoapBindingStub.java
> 
> --
> Tom Jordahl
> Macromedia Server Development
> 
> 
> 
> -----Original Message-----
> From: Sascha Kulawik [mailto:sascha@kulawik.de]
> Sent: Monday, December 09, 2002 11:19 AM
> To: axis-user@xml.apache.org; axis-dev@xml.apache.org
> Subject: AW: WSDL2Java - How to configure the Stubclasses name ?
> 
> 
> Tom,
> 
> Here is one of my (automagically created) WSDL's from a 
> Stateless Session Bean. Do I have to delete the created 
> Stubcode before creating a new one ? But I think, thats one 
> of many test I've made to create the Stubcode - I will get 
> everytime UnitSession_Port...
> 
> Regards,
> Sascha
> 
> -----Ursprüngliche Nachricht-----
> Von: Tom Jordahl [mailto:tomj@macromedia.com] 
> Gesendet: Montag, 9. Dezember 2002 15:54
> An: 'axis-user@xml.apache.org'; 'axis-dev@xml.apache.org'
> Betreff: RE: WSDL2Java - How to configure the Stubclasses name ?
> 
> 
> 
> Sascha,
> 
> As far as I know, no change to the file/class name generation 
> code has been made post 1.0. You can check the logic (which 
> is tricky) in the class
>   org/apache/axis/wsdl/toJava/JavaGeneratorFactory.java
> 
> See the resolveNameClashes() function.
> 
> The _Port and _Service suffixes (line 714 or so) are appended 
> to the class names when there is already an object of the same name.
> 
> Can you post your entire WSDL file?
> 
> --
> Tom Jordahl
> Macromedia Server Development
> 
> 
> 
> -----Original Message-----
> From: Sascha Kulawik [mailto:sascha@kulawik.de]
> Sent: Sunday, December 08, 2002 8:08 PM
> To: axis-user@xml.apache.org; axis-dev@xml.apache.org
> Subject: WSDL2Java - How to configure the Stubclasses name ?
> 
> 
> Hello,
> 
> I just want to use the same name for the Stubclass, as like 
> the Serverclass. Currently I've the problem with the 1.1beta 
> (and all following Nightly-Builds), that the Stubclass will 
> be called _Port, also the ServiceLocator isn't been called 
> ClassNameServiceLocator, it will be called 
> ClassName_ServiceLocator (all with Underlines). My problem is 
> not the ServiceLocator Name, more the name of the StubClass 
> Interface, who is now called ClassName_Port instead of ClassName.
> 
> I think, here is a complete change in the actual Axis 
> Version. Has anybody else also this effect ?
> 
> I'm using following ant-code for creating the stub-classes: 
> <target name="create-stub-ContentSession" depends="init">
>   <java classname="org.apache.axis.wsdl.WSDL2Java" 
> fork="true" failonerror="true" dir="${src.dir}">
> 	<arg value="http://${server}${server.path}ContentSession?wsdl"/>
> 	<classpath refid="project.class.path"/>
>   </java>
> </target>
> 
> Thank you very much for your help,
> 
> Sascha
> 
>