geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-1873) Deployment must handle dynamically-registered module builders
Date Thu, 16 Nov 2006 15:01:37 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1873?page=all ]

Matt Hogstrom updated GERONIMO-1873:
------------------------------------

    Fix Version/s: Wish List
                       (was: 1.2)

> Deployment must handle dynamically-registered module builders
> -------------------------------------------------------------
>
>                 Key: GERONIMO-1873
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1873
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>            Priority: Critical
>             Fix For: Wish List
>
>
> Currently the deployment infrastructure does some things specific to different module
types -- like identifying the embedded deployment plan in a xAR so it can look up the config
ID, and searching for child modules of an EAR.  This is currently hardcoded to the specific
set of module types supported by Geronimo by default.  It should be able to handle builders
deployed later (e.g. Spring, ServiceMix, whatever), which probably means it needs to be able
to ask something on the server-side what modules are available, what their nested plan files
are called, and what their j2eeType would be.

-- 
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