Could you debug into the EJBProvider, please? I will also have a look this afternoon (want to include MBeanProvider into xdoclet support, anyway) ...
CGJ -----Urspr�ngliche Nachricht----- Von: John Fawcett [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. April 2003 20:11 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-user] Different wsdl in jboss3.2 and jboss4.0 Hi, I am using jboss3.2RC5. I moved the axis libraries, and got the same wsdl. In addition, I moved the ibm-wsdl4j library, which also had no effect on the wsdl. Changing the libraries required minor changes to AxisService, AttributeSerializer, and ObjectNameSerializer -- should I submit a patch? Any other ideas to track down this change in the wsdl? Thanks, fawce -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jung , Dr. Christoph Sent: Thursday, April 03, 2003 10:13 AM To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-user] Different wsdl in jboss3.2 and jboss4.0 Which 3.2 are you talking about? I think that the difference between both branches is indeed Axis1.1 Beta (3.2) against Axis 1.1 RC1 (head) ... Our EJBProvider source should be equivalent by now. So it could be only the emitter setting the wrong servicename (to jndiName, as it seems). Can you please check by taking the head axis into 3.2? Btw: Thanks four your encouraging email. That made my whole day! CGJ -----Urspr�ngliche Nachricht----- Von: John Fawcett [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. April 2003 02:04 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-user] Different wsdl in jboss3.2 and jboss4.0 Correction, the naming convention in jboss3.2 appears to be: If(bean has local interface){ <sessionbeanlocaljndiname>Service } else { <sessionbeanjndiname>Service } Thanks, fawce -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Fawcett Sent: Wednesday, April 02, 2003 6:14 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] Different wsdl in jboss3.2 and jboss4.0 Hi, Until recently I have been working against a jboss-head checkout. The jboss.net in 4.0 creates a wsdl document that sets the wsdl:service name equal to the urn attribute in @jboss-net.web-service tag in my session bean. In 3.2, however, jboss.net produces a wsdl:service name equal to <urn>SessionLocalService. We are using these wsdl to auto-gen classes, and the classnames are derived from the wsdl:service names. So, our hand-made code makes references to these classnames which are not consistent between 3.2 and 4.0. Is the discrepency due to a difference in the axis libraries, ibm-wsdl4j, or ibm-uddi4j libraries? Or a difference in the jboss.net code? Is it possible to configure this suffix? Is one naming convention more likely to be maintained? Thanks, fawce Here is a sample: In jboss3.2: <wsdl:service name="EntityListSessionLocalService"> <wsdl:port binding="impl:EntityListSoapBinding" name="EntityList"> <wsdlsoap:address location="http://localhost:8080/jboss-net/services/EntityList"; /> </wsdl:port> </wsdl:service> In jboss4.0: <wsdl:service name="EntityList"> <wsdl:port binding="impl:EntityListSoapBinding" name="EntityList"> <wsdlsoap:address location="http://localhost:8080/jboss-net/services/EntityList"; /> </wsdl:port> </wsdl:service> ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
