geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sachin Patel <>
Subject Re: [jira] Resolved: (GERONIMO-1120) Auto-detect config ID for a deployable archive
Date Thu, 10 Nov 2005 14:11:39 GMT

Is there a way I can exploit this when invoking redeploy's through the 
DeploymentManager? Is there some utility method that can return me back 
a TargetModuleID for a given archive?  I currently have to traverse 
through all the TargetModuleID's returned from 
getDeploymentManager().getAvailableModule()'s to find a matching 
configID, and was wondering if there might be an easier way.

Aaron Mulder (JIRA) wrote:
>      [ ]
> Aaron Mulder resolved GERONIMO-1120:
> ------------------------------------
>     Resolution: Fixed
>      Assign To: Aaron Mulder
> Revision 332215
>> Auto-detect config ID for a deployable archive
>> ----------------------------------------------
>>          Key: GERONIMO-1120
>>          URL:
>>      Project: Geronimo
>>         Type: Improvement
>>   Components: deployment
>>     Versions: 1.0-M3
>>     Reporter: Aaron Mulder
>>     Assignee: Aaron Mulder
>>      Fix For: 1.0
>> Given an application/module/service archive, or an archive and a plan, we need a
routine to pull out what the configuration name will be for it.  In other words, we need to
peek into the deployment plan and look for the configId attribute, the catch being that we
don't know up front what the name of the plan file is if it's embedded in the JAR.
>> This is necessary to be able to redeploy without explicitly naming the configuration
to replace, which is necessary to do redeploy operations in a hot deploy directory.
>> It seems like it'd be easy to write a bit of code to do this by hardcoding the locations
of all known deployment types, but it would be a little more elegant if the deployers coughed
up the required information and it could be handled on a more pluggable basis.

View raw message