[ 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
