Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2176065.1150049730155.JavaMail.jira@brutus>
Date: Sun, 11 Jun 2006 18:15:30 +0000 (GMT+00:00)
From: "Alan Cabrera (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-1873) Deployment must handle
 dynamically-registered module builders
In-Reply-To: <9848375.1145493704401.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-1873?page=comments#action_12415777 ] 

Alan Cabrera commented on GERONIMO-1873:
----------------------------------------

How is this a bug and not an improvement?

> Deployment must handle dynamically-registered module builders
> -------------------------------------------------------------
>
>          Key: GERONIMO-1873
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1873
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Critical
>      Fix For: 1.1

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