<port-component-uri>/somepath/Portname</port-component-uri>to the section <port-component> of the EJB in the file jboss.xml
I am not using EJB deployment descriptors xml files as I am using EJB3 annotations exclusively.
Does this mean I need to generate a deployment descriptor (ie in the jboss.xml file) for the WebService EJB?
I haven't tried EJB3 so far. So I can only guess:
But as far as I know with EJB3 you only get rid of the ejb-jar deployment descriptor. If you deploy an ear you still need the application server specific deployment descripter (e.j. jboss.xml). As I said I haven' used EJB3, so I may be wrong at this point.
I hope this helps at least a little bit.
With EJB3 there appears there was a plan to place a "portName" field into the @WebService annotation. However it doens't seemed to have made it into the standard. I am using JDK 1.5.07 and portName is just not defined. It IS listed the O'Reilly EJB3 book as supported.
The main reason I wanted to change the name, was that I have a deployment dependency ordering issue between my jars. I was renaming my jars to have a numeric prefix such that they would be deployed in the correct order using the prefix based deployer. Having a url with http://hostname/03-webservicename/... looks a bit silly.
I have worked around it now by using the default URLDeploymentScanner and naming all jars that the webservice.jar is dependent upon with prefixes 01-, 02- etc and left the webservice.jar named without a numeral prefix. Numerals come alphabetically before "webservice.jar" so the default deployer seems to work OK now.
Have a look at @PortComponent which is a jboss propratary annotation