The implementation leverages the requirement that the 
<webservice-description-name> must be unique among all <webservice-description> 
elements within a given deployment.

It is also true that you can have multiple <port-component> elements within a 
<webservice-description> where the <port-component-name> must be unique as well.

I still favour the current implementation where it is the responsibility of the 
deployer to explicitly resolve the uniqueness of the multiple service endpoints 
within one <webservice-description>.

Adding <port-component-name> implilcitly to the <webservice-description-name> 
assumes that the combined path builds a valid URL and I am not a great fan of 
this.

I'll take this issue to the JSR-109 expert group. It is undefined how the 
endpoint address is built for an EJB endpoint. In contrary to this, for JSE 
endpoints it *is* defined - you must explicitly set the URL pattern in web.xml. 

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869123#3869123

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869123


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to