[ http://issues.apache.org/jira/browse/GERONIMO-1924?page=all ]
David Jencks updated GERONIMO-1924:
-----------------------------------
Assign To: Jeff Genender
This appears to be at least minimally fixed in rev 397614. Jeff, could you
review this and see if it looks OK?
> Need to register the tomcat jndi url handler somehow
> ----------------------------------------------------
>
> Key: GERONIMO-1924
> URL: http://issues.apache.org/jira/browse/GERONIMO-1924
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: Tomcat
> Versions: 1.1
> Reporter: David Jencks
> Assignee: Jeff Genender
> Priority: Blocker
> Fix For: 1.1
>
> Until recently we were using the Tomcat WebappLoader which has this code:
> // Register a stream handler factory for the JNDI protocol
> URLStreamHandlerFactory streamHandlerFactory =
> new DirContextURLStreamHandlerFactory();
> if (first) {
> first = false;
> try {
> URL.setURLStreamHandlerFactory(streamHandlerFactory);
> } catch (Exception e) {
> // Log and continue anyway, this is not critical
> log.error("Error registering jndi stream handler", e);
> } catch (Throwable t) {
> // This is likely a dual registration
> log.info("Dual registration of jndi stream handler: "
> + t.getMessage());
> }
> }
> This is how tomcat finds anything in the web app when you call
> servletContext.getResource(location_in_WEB_INF).
> Since we recently stopped using the tomcat classloader, we need to do this
> ourselves somewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
