[ http://issues.apache.org/jira/browse/GERONIMO-1875?page=all ]
Joe Bohn updated GERONIMO-1875:
-------------------------------
Attachment: 1875_RemoveDeps2.patch
This new patch (1875_RemoveDeps2.patch) results in a clean build and cleans up
many of the dependencies. Minimal-tomcat-server is around 20 meg. However,
there is an issue with starting applications on the big servers due to the
packaging rependencies. An invalid configuration because of not being able
to deserialize a gBean due to ClassNotFound .... ClassNotFoundException: Could
not load class org.openejb.corba.CORBAHandleDelegate$HandleDelegateReference
> 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_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
