geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Resolved: (GERONIMO-1120) Auto-detect config ID for a deployable archive
Date Thu, 10 Nov 2005 03:30:03 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1120?page=all ]
     
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: http://issues.apache.org/jira/browse/GERONIMO-1120
>      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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message