You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2006/04/20 02:41:44 UTC
[jira] Created: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
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
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
[jira] Assigned: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=all ]
Aaron Mulder reassigned GERONIMO-1873:
--------------------------------------
Assign To: Aaron Mulder
> 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
[jira] Commented: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=all ]
Matt Hogstrom updated GERONIMO-1873:
------------------------------------
Fix Version: 1.2
(was: 1.1)
> 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.2
>
> 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
[jira] Commented: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=comments#action_12375248 ]
David Jencks commented on GERONIMO-1873:
----------------------------------------
If this requires any action someone has really broken the deployer architecture. Be sure you are not confusing a config builder, of which there can be any number, and which can decide for themselves whether they can deploy something handed to them, and the module builders that plug into the EarConfigBuilder, which are designed to support j2ee artifacts. I don't know of anything hardcoded to a particular config builder. There is certainly nothing preventing deploying a spring or servicemix config builder.
> 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
> 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
[jira] Updated: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=all ]
Aaron Mulder updated GERONIMO-1873:
-----------------------------------
Assign To: (was: Aaron Mulder)
> 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
> Priority: Critical
> Fix For: 1.2
>
> 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
[jira] Commented: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=comments#action_12375334 ]
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: http://issues.apache.org/jira/browse/GERONIMO-1873
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1873) Deployment must handle
dynamically-registered module builders
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1873?page=comments#action_12375222 ]
Aaron Mulder commented on GERONIMO-1873:
----------------------------------------
See CommandSupport.loadChildren, for example
> 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
> 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