[
https://issues.apache.org/jira/browse/GERONIMO-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800641#action_12800641
]
Ashish Jain commented on GERONIMO-5027:
---------------------------------------
Here is what I have understood
Redeploy in geronimo is handled by a set of STOP, UNLOAD, UNINSTALL, INSTALL.
LOAD, START operations. In case of farming as there are set of nodes we will
have to obtain the JMX info of each of the nodes so as to get a kernel for each
of the nodes. Any of the deploy commands is executed by obtaning the meta data
and than calling up
the execute for the meta data. In case of farming install and uninstall are
taken care of by ConfigurationStore.install/uninstall.
In case of redeploy configuration manager is being used which is obtained
through COnfigurationUtil.getConfigurationManager(kernel).
There were various ways I have tried to achieve this for farming
1) To get the meta data for deploy and undeploy in redeploy, which is not
possible due to private constructors.
2) Extend the DeployTool to take up this case but this does not seem to be
correct to be specific for one funtionality.
3) Get the NodeInfo's in RedeployCommand and with some modifications to
artifact call up a series of STOP, UNLOAD, UNINSTALL, INSTALL. LOAD, START
operations.
There can be many other approaches which could be used of which I am not aware
of..
Comments please??
> Redeploy option for farming
> ---------------------------
>
> Key: GERONIMO-5027
> URL: https://issues.apache.org/jira/browse/GERONIMO-5027
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Clustering
> Affects Versions: 2.1.4, 2.2
> Environment: Windows XP g214
> Reporter: Ashish Jain
> Fix For: 2.1.5, 2.2.1
>
>
> Redeploy feature for farming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
