Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2630

Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar.

    XMLWordPrintable

Details

    • Hide

      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>
      <context-root>/Quickstart_webservice_consumer1</context-root>
      </jboss-web>

      Show
      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> <context-root>/Quickstart_webservice_consumer1</context-root> </jboss-web>

    Description

      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:
      http://127.0.0.1:8080/Quickstart_webservice_consumer1-Quickstart_webservice_consumer1/HelloWorldWS?wsdl
      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.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-5870 Cannot create JbossWS service with client enabled

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBWS-2776 WSDL unavailable for deployed web service in AS5.1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBWS-2332 Review and fix JBossWS integration with JBoss AS 5x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ropalka Richard Opalka
              dbeveniu Daniel Bevenius (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: