[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12659182#action_12659182 ] 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: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12654349#action_12654349 ] Delos Dai commented on GERONIMODEVTOOLS-540: Anyway, I agree with you, Francisco. It is a problem of Geronimo Devtools, so you don't have other chioce. I think the key to contaminate Tomcat is not the server path, but the deploy path. So, Geronimo Devtools may consider to set difference deploy path for workspaces, instead of deploy modules into the GERONIMO_HOME/repository. Does anyone know how to change the default deploy path of Geronimo Server? Thanks! Prevent geronimo contamination from deployments from multiple workspaces Key: GERONIMODEVTOOLS-540 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653600#action_12653600 ] Delos Dai commented on GERONIMODEVTOOLS-540: I found one thing interesting. If I select Use Tomcat installation, Tomcat still can't be contaminated. So I doubt is this option the key to the problem? Prevent geronimo contamination from deployments from multiple workspaces Key: GERONIMODEVTOOLS-540 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653605#action_12653605 ] Francisco Peredo commented on GERONIMODEVTOOLS-540: --- Yes, but in Tomcat, I can choose to contaminate it if I want to do so, in Geronimo I can not choose, I am forced to do it. Prevent geronimo contamination from deployments from multiple workspaces Key: GERONIMODEVTOOLS-540 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653607#action_12653607 ] Francisco Peredo commented on GERONIMODEVTOOLS-540: --- I have never wanted to contaminate Tomcat during development..., but if Use Tomcat installation does not contaminate it maybe it is a bug Prevent geronimo contamination from deployments from multiple workspaces Key: GERONIMODEVTOOLS-540 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
[jira] Commented: (GERONIMODEVTOOLS-540) Prevent geronimo contamination from deployments from multiple workspaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653172#action_12653172 ] Tim McConnell commented on GERONIMODEVTOOLS-540: Hi Francisco, it's interesting that you've requested this functionality. You might have noticed the greyed-out button in the Test Environment section of the server adapter properties page labeled: Run modules directly from workspace (you can see it in the first screenshot that you've attached). That button is meant to provide the capability to run deployed modules directly from the Eclipse workspace rather than the Geronimo repository, which is pretty much what you are asking for since you could then switch workspaces at will and not contaminate the common Geronimo server installation from any of the workspaces you use. Unfortunately though that button is greyed-out because it hasn't been fully implemented. I'm not exactly sure why not but I would guess because it hasn't been a high-priority requirement from many users. Also, it may be there that there just haven't been too many GEP users/developers who use multiple Eclipse workspaces with a common Geronimo installation. In any case, I'll do the initial analysis to see what is required to fully implement this function since obviously it's important to you. Thanks for bringing this to our attention. Prevent geronimo contamination from deployments from multiple workspaces Key: GERONIMODEVTOOLS-540 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-540 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.
