geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francisco Peredo (JIRA)" <>
Subject [jira] Updated: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
Date Thu, 04 Dec 2008 02:41:44 GMT


Francisco Peredo updated GERONIMODEVTOOLS-540:

    Attachment: screenshot-tomcat-adapter.jpg

> Prevent geronimo contamination from deployments from multiple workspaces
> ------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-540
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: New Feature
>          Components: eclipse-plugin
>            Reporter: Francisco Peredo
>            Assignee: Tim McConnell
>         Attachments: screenshot-tomcat-adapter.jpg
> When doing development of several independent applications over the Geronimo, that Geronimo
installation gets contaminated by those applications
> If I create workspaces1, and inside it I create dynamic webproject 1, and run it on Geronimo,
then I switch to workspace2, and create dynamic webproject 2, and run it on Geronimo, since
it is the same Geronimoinstance, 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 Geronimo.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message