geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <>
Subject Re: [moving-code] Boot time services to kernel module
Date Sun, 07 Sep 2003 06:39:25 GMT
Of course this turned into a massive effort... A list of the all of the 
code moved from core follows:

Moved to common module
   the entire package except AbstractManagedObject
   (we need this one here because boot services implement these 
   the entire package o.a.g.common from core module

Moved to kernel module
   the entire package o.a.g.deployment except model and repository
   GeronimoMBean* (I'm not sure about this one, but GermonimoMBean
       uses o.a.g.k.d.DeploymentException)

With this structure the we get a kernel that can boot with the 
following jars:
   commons-collections-SNAPSHOT.jar 464k
   commons-digester-1.5.jar 108k
   commons-jexl-SNAPSHOT.jar 112k
   commons-lang-SNAPSHOT.jar 168k
   commons-logging-1.0.3.jar 32k
   geronimo-common-DEV.jar 172k
   geronimo-kernel-DEV.jar 96k
   log4j-1.2.8.jar 348k
   mx4j-SNAPSHOT.jar 388k
   xerces-2.4.0.jar 876k
   xml-apis-1.0.b2.jar 108k

Which is 2.8 MB total.  I think we can remove the boot requirement on 
xerces and the xml-apis which would put us comfortably under 2MB.  I 
would love to get rid of commons-collections because it is a pig, but 
digester uses one class from it.

I'm going to sit on these changes until noon tomorrow CST (about 10 
hours from now), to give everyone due time complain.


On Saturday, September 6, 2003, at 06:53 PM, Dain Sundstrom wrote:

> Unless someone objects.  I'm going to move the boot time services code 
> to the kernel module.  The main motivation for this is the current 
> class loading is broken because the geronimo-core jar is booted on the 
> system class path so any service in core must have all of the classes 
> it depends on in the system class path.
> I am defining any boot time services as any code necessary load an 
> empty boot-service.xml file.  Since the boot-service.xml file can 
> define a class loader for the service in the file, we don't need to 
> include anything extra.  This will include the Main class and most of 
> deployment.
> -dain
> /*************************
>  * Dain Sundstrom
>  * Partner
>  * Core Developers Network
>  *************************/

View raw message