directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-787) ApacheDS tools should use the daemon classloader infrastructure to include jars in lib/
Date Tue, 13 Feb 2007 17:53:05 GMT


Alex Karasulu updated DIRSERVER-787:

    Affects Version/s: 1.0.1
        Fix Version/s:     (was: 1.5.0)
                           (was: 1.0.1)

This is a tough problem that requires quite a bit of effort.  I cannot dedicate the time to
fix this issue right now. 

Basically I need to break up the server-tools project into two separate projects so I 
can load the commands in a separate ClassLoader with all the jars in the lib and lib/ext 
directories on the classpath.  The ApacheDSTools launcher will need to go into it's 
own project for a executable jar then the rest of the classes in server-tools will be 
in another jar within the lib directory of the installation footprint.  This way the launcher

can build the CL and load the commands to invoke them.

This is quite a bit of work and I'd like to thoroughly test it. 

> ApacheDS tools should use the daemon classloader infrastructure to include jars in lib/
> ---------------------------------------------------------------------------------------
>                 Key: DIRSERVER-787
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 1.0.1, 1.0
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>             Fix For: 1.0.2
> Right now the apacheds-tools program does not use the special ClassLoader that adds all
jars in lib.  Instead it sets the bootclasspath using MANIFEST Classpath entries.  This is
really fragile and well breaks when new schemas are added to lib/ and when new interceptors
are added as well.  We should change this tool to use the daemon infrastructure to startup.
 It should only have the needed bootstrapper, and logger jars in it's MANIFEST Classpath.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message