[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2627) Allow adding deploy location to server deployment locations via JMX

[Rob Stryker (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated JBIDE-2627:
-------------------------------

    Summary: Allow adding deploy location to server deployment locations via JMX  (was: Add "Server Locations" option to JBoss WTP Adapter to prevent JBoss contamination)


Changing name so I can tell what it is more easily ;) 

> Allow adding deploy location to server deployment locations via JMX
> -------------------------------------------------------------------
>
>                 Key: JBIDE-2627
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2627
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 2.1.2
>            Reporter: Francisco Jose Peredo Noguez
>            Assignee: Rob Stryker
>             Fix For: 3.0.0.cr1
>
>         Attachments: screenshot-1.jpg
>
>
> When doing development of several independent applications over the  JBoss AS, that JBoss AS installation get contaminated by those applications 
> If I create  workspaces1, and inside it I create dynamic webproject 1, and run it on JBoss, then I switch to workspace2, and create dynamic webproject 2, and run it on JBoss, since it is the same JBoss instance, both dynamic webproject 1 and dynamic webproject 2 will start (and there is no way, from inside eclipse to undeploy dynamic webproject 1 unless I go back to workspaces1 and  undeploy it.
> But, if one is working with Tomcat, there is no problem, applications do not "contaminate" the shared Tomcat, why is that? well  the Tomcat WTP Adapter has a configuration option enabled by default under "Server Location",  that reads: "Use workspace metadata (does not modify Tomcat installation)". I would like to have an option like that for JBoss AS.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira