directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marian Schedenig (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSERVER-1504) DefaultSchemaLdifExtractor relies on "java.class.path" environment variable
Date Tue, 18 May 2010 16:46:44 GMT
DefaultSchemaLdifExtractor relies on "java.class.path" environment variable
---------------------------------------------------------------------------

                 Key: DIRSERVER-1504
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1504
             Project: Directory ApacheDS
          Issue Type: Bug
    Affects Versions: 1.5.7
         Environment: Tomcat 6.0.26, Sun JDK 1.6.0_16, Windows Vista
            Reporter: Marian Schedenig
            Priority: Critical


When initialising ApacheDS, DefaultSchemaLdifExtractor is invoked by to read default LDIF
files. To find these files, regular expressions are applied to all JARs found in the class
path. The class path is found by reading the environment variable "java.class.path".

This is done in ResourceMap#getResources():

        String classPath = System.getProperty( "java.class.path", "." );
        String[] classPathElements = classPath.split( File.pathSeparator );

There is no guarantee that "java.class.path" contains all the JARs available to the current
class loader. For example, in Tomcat 6, the variable only contains one single entry, Tomcat's
own bootstrap.jar. Result: DefaultSchemaLdifExtractor fails to find and extract any LDIF files,
and JarLdifSchemaLoader throws an exception when an expected schema file is not available.


-- 
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