[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-473) JBoss AS ignores context root property of dynamic web project

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606712#comment-12606712 ] 

Rob Stryker commented on JBIDE-473:
-----------------------------------

Well what is your suggested behavior to supporting them? The only thing I could do really is check the context-root flag and then override all OTHER settings for what the deployment name should be. Then we'd run into situations where a user says they have ProjectA, but on the deployment page of Server Z, they want it to be deployed as ProjectB.  But, in the component.xml file, they have archive-name set to ProjectC, and they also want the context root to be ProjectD. 

There are already entirely too many places to change the output name of a jar / war / ear,  and users will quickly get confused as to which values override which others. It's ridiculous. 

Tomcat has a descriptor file sitting in their deploy folder that directly lists every deployment to register, and what the context root should be. JBoss has no such thing, as far as I know, and thus, the only way I can change the context root, is by changing the deploy name. There was once a time where the generic web app descriptors would list context root, but the dynamic of stopping users from changing the descriptor file was deemed not intuitive... 

So I'd like to see what exactly you are suggesting for behaviour here, because I for one am pretty well stuck. 

> JBoss AS ignores context root property of dynamic web project
> -------------------------------------------------------------
>
>                 Key: JBIDE-473
>                 URL: https://issues.jboss.org/browse/JBIDE-473
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>            Reporter: Viacheslav Kabanovich
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.M3
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira