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 2013/07/21 22:44:47 UTC
[Bug 55287] New: ServletContainerInitializer in parent classloader
may not be found
https://issues.apache.org/bugzilla/show_bug.cgi?id=55287
Bug ID: 55287
Summary: ServletContainerInitializer in parent classloader may
not be found
Product: Tomcat 8
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: jboynes@apache.org
To include the JasperInitializer in the test environment I added an entry in
testclasses/META-INF/services. This is not picked up when the parent
classloader is searched because this path is a directory not a JAR file.
It would be picked up if the "scanAllDirectories" extension was enabled but
that should not be necessary if the search is to be semantically equivalent to
j.u.ServiceLoader (which does locate it).
--
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
[Bug 55287] ServletContainerInitializer in parent classloader may
not be found
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55287
Jeremy Boynes <jb...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |55312
--
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
[Bug 55287] ServletContainerInitializer in parent classloader may
not be found
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55287
--- Comment #1 from Jeremy Boynes <jb...@apache.org> ---
Looking at StandardJarScanner, it also only looks for services where the
ClassLoader is a URLClassLoader whereas j.u.ServiceLoader basically uses
getResources() on the supplied ClassLoader.
--
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
[Bug 55287] ServletContainerInitializer in parent classloader may
not be found
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55287
Jeremy Boynes <jb...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Jeremy Boynes <jb...@apache.org> ---
Fixed in trunk: http://svn.apache.org/r1507870
--
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
[Bug 55287] ServletContainerInitializer in parent classloader may
not be found
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55287
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
This has also been fixed in 7.0.x for 7.0.51 onwards.
--
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