DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34746>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34746 Summary: Specifying an explict jar file pathname in shared.loader property fails Product: Tomcat 5 Version: 5.0.30 Platform: Sun OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] 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. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
