[
http://jira.jboss.com/jira/browse/JBIDE-473?page=comments#action_12375958 ]
Rob Stryker commented on JBIDE-473:
-----------------------------------
There are two ways I know to set the context root in a deployment:
1. Via the name of the archive (ie, ourproject.war)
2. Via the jboss-web.xml
I think it's probably easier to simply rename the output file rather than try to stick
my hands in the jboss-web.xml.
This will lead to inconsistancy, though, if a user sets the context root via the pulldown,
but then has a different value in the jboss-web.xml.
JBoss AS ignores context root property of dynamic web project
-------------------------------------------------------------
Key: JBIDE-473
URL:
http://jira.jboss.com/jira/browse/JBIDE-473
Project: JBoss Tools
Issue Type: Feature Request
Reporter: Viacheslav Kabanovich
Assigned To: Rob Stryker
Open editor for Tomcat Server (double click Tomcat node in Servers view). The editor has
two tabs - Overview and Modules. In Modules tab, it is possible to select a registered web
project and call dialog for changing path (context root) property by Edit button. Then,
for example, if project's name is MyProject but path is set to /OurProject, in order
to access the application running on Tomcat server one has to type in browser an address
like
http://localhost:8080/OurProject rather than
http://localhost:8080/MyProject.
Red Hat studio defines menu action 'Register Web Context in Server', which
invokes dialog that allows to set context root property. That works fine with Tomcat
server, but fails with JBoss AS, because it seems that its implementation ignores this
property of web project when deploying it. Hence, the request is to develop this
functionality of JBoss AS to the level of Tomcat server.
Context root property is accessible through class
org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities with methods
public static void setServerContextRoot(IProject project, String contextRoot)
public static String getServerContextRoot(IProject project)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira