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=6139>. 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=6139 Jars in WEB-INF/lib are not always reloaded when context is removed and added again ------- Additional Comments From [EMAIL PROTECTED] 2002-01-31 07:15 ------- The only consequences that I know of is that the ClassLoader won't inforce Java2 Manifest constraints (e.g. sealing). And even this one I actually haven't confirmed fails. If you can (possibly) live without sealing, then I can't see any reason not to use this in production. And AFAIK, the reporter of 5684 is using it in production. Actually, 5684 continued for awhile on the "Developers List" before finally getting resolved. That's probably why the attribute didn't show up on bugzilla. However, it is documented in the "/doc/serverxml.html" document in 3.3.1-dev. Also, if the context is marked as "reloadable" (not normal for production), then you should be able to replace the jar file without stopping and starting the context. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
