geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Delos Dai (JIRA)" <>
Subject [jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
Date Thu, 25 Dec 2008 03:14:44 GMT


Delos Dai commented on GERONIMODEVTOOLS-540:

Hi, All

About the deploy path, I think devtool can't have the same behavior as the adapter for Tomcat.
Because, currently all the module deployed on Geronimo is recorded in <GERONIMO_HOME>/var/config/config.xml.
It's a global config file and currently, as I know, no way to specify config.xml in another
position. So even if a module were deployed in a different position(not in repository), it
would also be recorded in the global config file.In this case, once the position doesn't exist
anymore, server won't start successfully.

However, this feature is to "prevent geronimo contamination from deployments from multiple
workspaces".So  although Geronimo can't has same behavior as Tomcat, we can prevent the contamination.
Maybe two method can be performed. 

1) First method  is to stop modules not in workspace,but plugin is not taken into account
because we can't distinguish which plugins is neccessary for server or not. We can also consider
plugins as part of server itself and can't be separated by devtools.

To enable "Run modules only from workspace", it means only launch the modules in workspace
and don't launch the modules deployed on server but not in current workspace. For this, when
server is started and "Run modules only from workspace" is selected, devtool will compare
the  running modules on server and modules in workspace by module id. If modules running 
in server (these modules shouldn't be plugins,  has been part of  doesn't in the module list
of workspace, these modules will be stopped. When server is stopping in eclipse, these stopped
modules will be restarted before server is stopped.  

2) Another method is to undeploy current modules in workspace, which are deployed on server
when server is stopping. In this case , maybe it's more proper to change "Run modules only
from workspace" into "Keep deployed modules on server". If this item is selected, modules
will not be undeployed from server when server is stopping.Otherwise, modules will be undeployed.

I attach the patch 540_1 for method 1 and 540_2 for method 2.

I'm not sure they're the only methods for this feature.  If any function of server supporting
this can be told, that will be wonderful. 

Any comments?

Thanks a lot!


> Prevent geronimo contamination from deployments from multiple workspaces
> ------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-540
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: New Feature
>          Components: eclipse-plugin
>    Affects Versions: 2.2.0, 2.1.4
>            Reporter: Francisco Peredo
>            Assignee: Tim McConnell
>         Attachments: screenshot-1.jpg, 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