Letting an application cleanup a resource created by the server is also not very nice.
Dirk
[EMAIL PROTECTED] wrote:
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=22626>.
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=22626
Removing a webapp(context) doesn't close its datasources(resource)
[EMAIL PROTECTED] changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2003-08-22 06:44 ------- Tomcat JNDI uses the object factory mechanism. This does not define an API to release resources. As such, it is up to the webapp to release resources if needed, and I am currently against implementing a DBCP hack.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
