I believe from the various threads on the Resources implementation for Tomcat 8 there is agreement that:
- DirContext is not the right basis for the Resources API - Refactoring is required to simplify the multiple 'add-ons' and to provide a sound basis for overlays (which may slip to Servlet 3.2) - Any Resources implementation must provide in-memory caching The sandbox Resources implementation addresses all of the above and passes the Servlet and JSP TCKs as well as all the unit tests. Given the above, is there any objection to merging the changes made in the sandbox back to trunk? Note that the following TODOs remain: - Provide an option to exclude selected resources from the cache - Remove the DirContext code - Review the use of trailing '/' - Determine if a custom URL scheme is required (and implement if it is) - Review the interaction of WebappClassLoader and Resources to see if there current work-arounds are a) still required b) implemented efficiently Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
