Hi Thomas, Even if you do not accept this as a bug, it is an issue that JBossWS should look into. If you need the port-component-uri to be hardcoded, that's a serious portability issue for the EAR.
Anyway, if the whole point is to get two unique URIs like http://somehost:8080/myservice/bean-one http://somehost:8080/myservice/bean-two then why can't JBoss deployer obtain the names 'bean-one' and 'bean-two' either from webservices.xml (<port-component><port-component-name> element). Otherwise, what do you expect to be put in a port-component-uri in jboss.xml? I tried something like http://somehost:8080/myservice/bean-one and it failed with the exception that it couldn't understand 8080/... portion. What exactly is expected?? XB View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886581#3886581 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886581 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
