[
https://jira.jboss.org/jira/browse/JBIDE-2627?page=com.atlassian.jira.plu...
]
Gabriele Garuglieri commented on JBIDE-2627:
--------------------------------------------
Actually you have a couple of ways to use different deployment dirs without copying around
installation dirs.
1- use the mbean "jboss.deployment:type=DeploymentScanner,flavor=URL" method
addURL() via jmx after server startup to dynamically add a deployment directory. This must
be done each time the server is restarted and you are still using the working dirs set of
the installation.
2- use the ${jboss.server.base.dir}, ${jboss.server.base.url} and ${jboss.server.name}
configuration properties to setup different server instances for each server definition in
eclipse.
In this way you need to twiddle a bit the jboss-service.xml (into
${jboss.server.base.dir}/${jboss.server.name}/conf) to include
${jboss.home.dir}/server/default/deploy into the directories scanned for deployment.
This is what i use, in combination with service-bindings.xml, so that i can have multiple
instances active at the same time(ref
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=143827). Respect to the
former, this way gives the option to use, with a single installation, completely different
set of working dirs (deploy, data, log, tmp, etc.) for each instance, avoiding possibility
of any contamination and even build clustered configurations (if the pc processor and
memory can cope with it).
It would be great if the server component of JBoss Tools could add support these
configuration options.
Add "Server Locations" option to JBoss WTP Adapter to
prevent JBoss contamination
---------------------------------------------------------------------------------
Key: JBIDE-2627
URL:
https://jira.jboss.org/jira/browse/JBIDE-2627
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
Fix For: 3.0.0.beta1
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