geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1873) Deployment must handle dynamically-registered module builders
Date Thu, 20 Apr 2006 11:17:06 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-1873:

You can deploy the builder.  But if you try to redeploy a Spring *application* using that
builder, the deploy tool won't be able to figure out the config ID of the application you're
trying to redeploy, and you'd need to specify it on the command line.  Likewise when looking
for children of an EAR, it wouldn't find Spring modules, so it wouldn't show them in a list
of children for that EAR.

> Deployment must handle dynamically-registered module builders
> -------------------------------------------------------------
>          Key: GERONIMO-1873
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>     Reporter: 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:
For more information on JIRA, see:

View raw message