DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3902>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3902 lib/apps jar files [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2001-10-01 14:29 ------- My test web application that checks class visibility is able to detect classes in lib/apps from the web application class loader. Note however, the documentation doesn't show that "trusted" web applications sit above the Server classloader rather than above the Apps classloader. As a result "lib/apps" isn't visible to "trusted" web applications. This is deliberate so that jars placed in "lib/apps" can be shared amoung web applications (non-trusted) without impacting server operation. If "lib/apps are not picked up by application contexts" is refering to something else, please supply more detail and if possible a jar to go in "lib/apps" and a simple webapp that has a problem accessing the jar.
