Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <27860933.1171344967529.JavaMail.jira@brutus>
Date: Mon, 12 Feb 2007 21:36:07 -0800 (PST)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Assigned: (DIRSERVER-787) ApacheDS tools should use the
 daemon classloader infrastructure to include jars in lib/
In-Reply-To: <9608114.1165075160964.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Karasulu reassigned DIRSERVER-787:
---------------------------------------

    Assignee: Alex Karasulu

> 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
>            Reporter: Alex Karasulu
>         Assigned To: Alex Karasulu
>             Fix For: 1.0.1, 1.5.0
>
>
> 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.