[GERONIMO-1120] Auto-detect config ID for a deployable archive

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-M3
• Fix Version/s: 1.0
• Component/s: deployment
• Security Level: public (Regular issues)
• Assignee: Aaron Mulder
• Reporter: Aaron Mulder
• Created: 31/Oct/05 12:07
• Updated: 02/May/13 02:28
• Resolved: 10/Nov/05 12:29

Description

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.

Issue Links

• is depended upon by: GERONIMO-686 Directory based hot deployment support
• is depended upon by: GERONIMO-804 Redeploy should calculate ModuleID to replace if not provided