DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38667>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38667 Summary: [pool] proposed ObjectPools.close JavaDoc changes for 2.0 Product: Commons Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Keywords: PatchAvailable Severity: enhancement Priority: P3 Component: Pool AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Attached are the pool 2.0 changes I'd like to see to the ObjectPool and the KeyedObjectPool interfaces for the close method. This change also affects the addObject and borrowObject methods. The noteworthy changes are: * Calling ObjectPools.close method in addition to freeing resources makes it so any future calls to addObject and borrowObject will thrown an IllegalStateException because the pool is now closed. * ObjectPools.close methods currently are declared to throw Exception. This has been documented as deprecated and I hope to remove the throws clause in Pool 3.0. * The addObject and borrowObject JavaDocs have been updated to indicate when and why they would throw an IllegalStateException. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
