Bug 34746 - Specifying an explict jar file pathname in shared.loader property fails
Summary: Specifying an explict jar file pathname in shared.loader property fails
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 5.0.30
Hardware: Sun other
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2005-05-04 21:01 UTC by Bill Edwards
Modified: 2005-07-21 13:57 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Bill Edwards 2005-05-04 21:01:15 UTC
When specifying an explicit jat file path name in the shared.loader
property of catalina.properties file, the jar file is not loaded.

The problem occurs between the Bootstrap.createClassLoader method
and the StandardClassLoader.addRepositoryInternal method.
In the form method, a File instance is created in which the
path name has a File.separator appended.  This occurs only if
the resource path ends with ".jar" and does not end with "*.jar".
In the latter method, the pathname in the File instance passed
in the "unpacked" parameter is checked to see if it ends with
the "/" character.  If so, it is not opened and its manifest
is not added to the opened Jars.

To workaround, simply make the explicit jar file pathname a
URL; that is, prefix its path with "file:" in the shared.loader
property in catalina.properties.
Comment 1 Yoav Shapira 2005-06-01 04:13:28 UTC
So, I'm guessing you'd like us to update the documentation to reflect the
Comment 2 Yoav Shapira 2005-07-21 21:57:32 UTC
Documentation clarified per your instructions: thanks.