Backwards incompatibility in deployment --------------------------------------- Key: JBESB-2910 URL: https://jira.jboss.org/jira/browse/JBESB-2910 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Lukáš Petrovický Behavior of a scenario where an ESB archive contains a WAR archive has significantly changed. On SOA-P 5.0.0 ER1, if the WAR doesn't include a WEB-INF/jboss-web.xml file containing a <context-root /> specifying the context root for the web service, the endpoint becomes available with a different context root (and URL) than before. This can be observed for example with the webservice_consumer1 QS. If the stock QS is used, deploying its ESB archive produces following in the log: 2009-10-26 08:19:13,597 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (HDScanner) register: jboss.ws:context=Quickstart_webservice_consumer1,endpoint=HelloWorldWS That is the SOA-P 4.x behavior. However, when the WAR's jboss-web.xml file is removed (and thus the context root isn't defined), following is produced in the log: 2009-10-26 08:16:10,275 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (HDScanner) register: jboss.ws:context=Quickstart_webservice_consumer1-Quickstart_webservice_consumer1,endpoint=HelloWorldWS If this is an intentional incompatibility, it needs to be well documented. -- 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