So, for example, I have the following header:
/** * @ejb.bean name="TransactionProcessor" * local-jndi-name="TransactionProcessor" * type="Stateless" * view-type="local" * @jboss-net.web-service urn="TransactionProcessor" */
which generates:
<deployment
name="TransactionProcessorService"
...
<service name="TransactionProcessor" provider="Handler">
<parameter name="handlerClass" value="org.jboss.net.axis.server.EJBProvider"/>
<parameter name="beanJndiName" value="TransactionProcessor"/>
...
</deployment>
And is output by Axis as:
<wsdl:definitions>
...
<wsdl:service name="TransactionProcessorLocalService">
<wsdl:port binding="impl:TransactionProcessorSoapBinding" name="TransactionProcessor">
<wsdlsoap:address location="http://localhost:8080/jboss-net/services/TransactionProcessor"/>
</wsdl:port>
</wsdl:service>
...
</wsdl:definitions>
I never noticed this before because I've used remote session beans. Not sure if it is a bug or just a limitation in the current implementation.
Rob
Jason Essington wrote:
Rob
The @jboss-net.web-service tag has a parameter "urn" which can be used to set the service name something like:
* @jboss-net.web-service * urn="MySessionService" * expose-all="true"
-jason
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user