Status: Closed (View Workflow)
Affects Version/s: jbossws-metro-3.1.1, jbossws-cxf-3.1.2, jbossws-native-3.1.2
Alessio provided us with a solution where we could simply add a WEB-INF/jboss-web.xml and there specify a context root:
<?xml version="1.0" encoding="UTF-8"?>
</jboss-web>ShowAlessio provided us with a solution where we could simply add a WEB-INF/jboss-web.xml and there specify a context root: <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <context-root>/Quickstart_webservice_consumer1</context-root> </jboss-web>
Similar Issues:Show 10 results
JBWS-2443 services page does not correctly update host address of endpoints JBWS-1472 Address in WSDL is now always replaced regardless of 'alwaysModifySOAPAddress' value. JBWS-2155 Not supporting JMS endpoints for WS-Addressing JBWS-3797 Let @WebContext(virtualHost...) affect endpoint address JBWS-3343 Support for both EJB3 and POJO WS endpoints in war archives JBWS-1655 Add support for endpoint address rewriting JBWS-3198 EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR JBWS-1093 Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints JBWS-523 Interoperability: Test WS-Addressing Endpoints JBWS-1937 Document/Literal addressing endpoint fails when retreiving Outbound Action
I noticed this when working on getting examples for JBossESB running on JBoss AS 5. We have .esb archives (jar archives) that can contain a .war inside of them.
For example, we have a quickstart that is named Quickstart_webservice_consumer1.esb which contains a Quickstart_webservice_consumer1.war.
Deploying this on AS 5 will produce the following "Endpoint Address" in http://localhost:8080/jbossws/services:
But if I try to access that the resource is not found.
I was not sure about the component for this. The ContextServlet exists in the jbossws-framework project but I don't know if that maps to one of the components in the dropdown.