https://issues.apache.org/bugzilla/show_bug.cgi?id=51744
--- Comment #12 from Mark Thomas <ma...@apache.org> 2011-10-27 16:11:07 UTC --- To quote from section EE.5.3.4 of the Java EE spec <quote> The container must ensure that the application component instances have only read access to their naming context. The container must throw the javax.naming.OperationNotSupportedException from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts. </quote> I would argue that the close() method is a method that "modifies the environment naming context" and therefore an exception should be thrown here. Tomcat is, however, not throwing the right exception in this case. Fortunately, the exception we should be throwing is a sub-class of the one we are throwing so changing it shouldn't break anything. Providing an option on the StandardContext to silently swallow this error rather than throwing an Exception looks doable. I'll take a look. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
