1 Reply Latest reply on Jul 10, 2014 4:57 PM by sdoca

    Understanding App Deployment - Context Root and URL

    sdoca

      Hi,

       

      I am just getting started with JBoss EAP 6.2 coming from Glassfish.  I have a war file that is a JAX-RS web service and am deploying it thru the admin console.  On step 2 of the "Create Deployment" screen, it has the following fields, Key, Name and Runtime Name.

       

      What is the difference between Name and Runtime Name?

       

      I initially thought Runtime Name was the context root of the deployed applcication and changed it to what I wanted in my URL, but if I change it, I am unable to Enable the application.  I have since learned about setting the context in the jboss-web.xml file.  So, I added  the file with these contents:

       

      <jboss-web>

          <context-root>processor</context-root>

      </jboss-web>

       

      I can deploy and enable the app and when I check the web | deployment tab of the app it shows that the context root is "/processor".  However, when I try to access the app via this URL, http://localhost:8080/processor/rs (my JAX-RS Application class is annotated with @Path("rs") ), I get a 404 error.

       

      How do I figure out what the URL of my application is?  In Glassfish, I would just click on the "launch" link and it would show me the possible URLs.

       

      Thanks!

        • 1. Re: Understanding App Deployment - Context Root and URL
          sdoca

          I found that changing my web.xml from this:            DVCProcessor                    org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher                            javax.ws.rs.Application            ca.shaw.tno.oss.dvc.processor.resource.ProcessorResource                1    to this:            DVCProcessor                    org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher                1    

                      resteasy.scan        true    allowed me to access my app.

          Can't figure out how to use this editor to display the web.xml snippets correctly...  :(