You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2009/07/07 09:35:43 UTC

DO NOT REPLY [Bug 45785] ClassCastException if directory ending with .jar exists in WEB-INF/lib

https://issues.apache.org/bugzilla/show_bug.cgi?id=45785





--- Comment #3 from Rolf Wojtech <ro...@wojtech.de>  2009-07-07 00:35:40 PST ---
Created an attachment (id=23934)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23934)
Add support for directories with name ending on .jar

While the specific case (directory called .jar in WEB-INF/lib) has been fixed,
two other cases remain in ExtensionValidator.

Therefore I reopened this bug:

We're using an exploded deployment mechanism which uses extracted jar files in
folders called jarname.jar. The eclipse projects build directly into those
folders.
However when adding these projects to a jboss launch configuration, which
results in a jarname.jar folder (not file) to be part of the classpath, JBoss
will fail because ExtensionValidator tries to treat the jarname.jar folder as a
file.
ExtensionValidator only checks if a java.io.File endsWith(".jar") but it fails
to check if it is an actual file, not a directory.

I attached a proposed fix (I only added the !item.isDirectory() and
!files[i].isDirectory() )

I ran into other JBoss problems after fixing this which means that this does
not really affect me. It may not be popular to name directories something.jar
but in the cases of exploded deployment this seems normal. In any case my patch
does not affect the normal usage of actual .jar files so I see no reason not to
include it.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org