When a web service inside an ESB archive is deployed in a way that the WAR doesn't contain the WEB-INF/jboss-web.xml file (SEE JBESB-2910 for a full description of the problem), the WSDL of the web service becomes inaccessible.
As an example, take the webservice_consumer1 quickstart with its WAR updated, so that it doesn't contain the file above. (I can attach it, if necessary.) When we deploy it, we see the following (using JBossWS console) as an endpoint address for the WS:
This address, when accessed with a browser, returns HTTP 404. When we blindly try the address that this WS would've had in SOA-P 4.x, we get HTTP 500 (Servlet Exception):