You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/04/29 00:01:38 UTC

[jira] Closed: (GERONIMO-1875) More work to port little-g to 1.1

     [ http://issues.apache.org/jira/browse/GERONIMO-1875?page=all ]
     
David Jencks closed GERONIMO-1875:
----------------------------------

    Resolution: Fixed

This stage of minimization seems complete.  If there are more problems we'll open new issues.

> More work to port little-g to 1.1
> ---------------------------------
>
>          Key: GERONIMO-1875
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1875
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>     Versions: 1.1
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.1
>  Attachments: 1875_RemoveDeps.patch, 1875_RemoveDeps2.patch, 1875_RemoveDeps3.patch, 1875_axis+builder+clientDeploy.patch, 1875_axis+builder.patch, 1875_littleg.patch, 1875_openejb-deployer.diff
>
> This issue will be used to hold more patches for little-g modularization of geronimo 1.1.  Some pieces:
> - additional plans for new configs
> - turning single valued references to ejb builder, axis builder, client builder, connector builder etc into something that will work.  The problem is that all these builders can't be in the ancestor tree of j2ee-deployer, or we'd always be pulling them into the server.  Therefore they need to be collection valued references.  We can make a collection wrapper that returns a single element or null, or objects to the presence of more than one element, and use this to hold many of these  0..1 valued references.  Both EarConfigBuilder and ClientModuleBuilder need this modification.
> - modify existing plans to remove gbeans now in the new plans. Be sure to update the defaultEnvironments as appropriate.
> - modify the assemblies.

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