[
https://jira.jboss.org/jira/browse/JBESB-2911?page=com.atlassian.jira.plu...
]
Lukáš Petrovický commented on JBESB-2911:
-----------------------------------------
I don't think this is an issue with JBossWS - this can only be seen with a WAR that
comes from inside ESB archive; the behavior of a "standalone" WAR in this case
would be exactly the same, with jboss-web.xml present or not. For this reason, I think
this is an issue in ESB deployer, although I may (of course) be wrong.
The relevant parts of ESB quickstarts have been modified to reflect this change - and all
the ESB "customers" will have to do the same for their services that have their
own WARs inside the ESB archive.
Web Service without context-root inside ESB archive has inaccessible
WSDL
-------------------------------------------------------------------------
Key: JBESB-2911
URL:
https://jira.jboss.org/jira/browse/JBESB-2911
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Lukáš Petrovický
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:
http://localhost:8080/Quickstart_webservice_consumer1-Quickstart_webservi...
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):
http://localhost:8080/Quickstart_webservice_consumer1/HelloWorldWS?wsdl
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira