[JBoss-user] Different wsdl in jboss3.2 and jboss4.0

[John F. <jfa...@ta...>]

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>