directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-787) ApacheDS tools should use the daemon classloader infrastructure to include jars in lib/
Date Fri, 20 Apr 2007 02:03:15 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490220
] 

Alex Karasulu commented on DIRSERVER-787:
-----------------------------------------

At this point I don't know if this is worth doing.  I'm wondering if splitting this module
into two and perhaps mucking with the daemon bootstrappers is too invasive of a change for
a maintenance release.  

Thoughts?

> ApacheDS tools should use the daemon classloader infrastructure to include jars in lib/
> ---------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-787
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-787
>             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.


Mime
View raw message