> -----Original Message----- > From: Tom Jordahl [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 4:21 PM > To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' > Subject: RE: Java2WSDL - Bug found on generating the > wsdl:service Name by java:EJB Provider > > > Sascha, > > Several things have changed in in the WSDL generation since > 1.0, mainly to support faults and better document/literal > WSDL. In the course of this work, some of the WSDL element > names that are generated may have been changed. If you could > describe exactly the differences in behavior, we might be > able to change it back, but then again, this new behavior > might be more correct and you would have to adapt your client > code to the new names.
My steps are easy: I have Axis deployed in JBoss3.0.4_Tomcat4.1.12 - also there resists the Stateless Session Beans I'm exporting through Axis. In my server-config.wsdd i have follwing entrys for each session bean: <service name="UnitSession" provider="java:EJB"> <parameter name="allowedMethods" value="addUser2Unit, createUnit, getContents4Unit, getEditors4Unit, getRootUnit, getUnit4Name, getUnits, isTrue, removeUnit, removeUserFromUnit, updateUnit"/> <parameter name="remoteInterfaceName" value="de.juwimm.cms.interfaces.UnitSession"/> <parameter name="beanJndiName" value="cmr.UnitSession"/> <parameter name="homeInterfaceName" value="de.juwimm.cms.interfaces.UnitSessionHome"/> </service> Also I'm using following Mappings for each Bean: <beanMapping languageSpecificType="java:de.juwimm.cms.dao.UnitDao" qname="ns14:UnitDao" xmlns:ns14="urn:dao.cms.juwimm.de"/> <beanMapping languageSpecificType="java:de.juwimm.cms.interfaces.UserData" qname="ns15:UserData" xmlns:ns15="urn:interfaces.cms.juwimm.de"/> Then I access the service through servername/axis/services/UnitSession?wsdl Following is a part from the 1.0 Axis WSDL: <wsdl:service name="UnitSessionService"> <wsdl:port name="UnitSession" binding="impl:UnitSessionSoapBinding"> <wsdlsoap:address location="http://localhost/axis/services/UnitSession"/> </wsdl:port> </wsdl:service> Following is a part from the 1.1 Axis WSDL: <wsdl:service name="UnitSession"> <wsdl:port name="UnitSession" binding="impl:UnitSessionSoapBinding"> <wsdlsoap:address location="http://testserver/axis/services/UnitSession"/> </wsdl:port> </wsdl:service> And like your previous Mail, there is a Problem with the same Name as Port Name and as Service Name I will get every Bean as UnitSession_Port exported. Tom: Do you know, why there could be serialization problems using german umlauts inside a String ? As seen through the TCPMon I will get every umlaut serialized by the Axis Client as - for example - & # 2 5 2 ; (without spaces) and the service (Session Bean) on the Serverside won't recognize this correctly. The problem is, that I don't use any Proxy Code, where I can trace and debug. So the Session Bean will get already the wrong String... Regards, Sascha > > > -----Original Message----- > From: Sascha Kulawik [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 5:54 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Java2WSDL - Bug found on generating the > wsdl:service Name by java:EJB Provider > > > 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:[EMAIL PROTECTED]] > > Sent: Monday, December 09, 2002 5:57 PM > > To: '[EMAIL PROTECTED]' > > 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:[EMAIL PROTECTED]] > > Sent: Monday, December 09, 2002 11:19 AM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > 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:[EMAIL PROTECTED]] > > Gesendet: Montag, 9. Dezember 2002 15:54 > > An: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' > > 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:[EMAIL PROTECTED]] > > Sent: Sunday, December 08, 2002 8:08 PM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > 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 > > > > > >
<<attachment: winmail.dat>>
