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 2019/11/26 15:10:41 UTC

[Bug 63964] Null returned when opening resource URL stream

https://bz.apache.org/bugzilla/show_bug.cgi?id=63964

Remy Maucherat <re...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Remy Maucherat <re...@apache.org> ---
Given this and other posts in the user list, I think there's an issue with the
URL resolution that was added.

Trying to have a full implementation may lead up to the Tomcat 7 resources
complexity it seems (except without JNDI and the custom protocol, but this
strategy had its own benefits if you want a full implementation that worked in
all cases), because next time we'll have someone asking "oh and if I do
servletContext.getResource("/WEB-INF/dir/").toString() + "/myPath" I have an
inconsistent result", which is basically what people spent months spamming me
about during the Tomcat 5 days. Maybe the URL stream handler should be reverted
and the JSP recompilation "issue" (a 100% brain dead use case) and other
similar possible inconsistencies should be documented as wontfix instead of
venturing again into that nest of spiders.

-- 
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