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=14983>. 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=14983 GenericObjectPool should allow for manual population of the pool Summary: GenericObjectPool should allow for manual population of the pool Product: Commons Version: 1.0.1 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Pool AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I need an ObjectPool which blocks when exhausted and is populated manually by the client. Wouldn't it be nice if GenericObjectPool provided this? I don't see how adding this capability would detract from any existing functionality. All we need is a new method, addNewObject(), whose implementation is very similair to, but NOT the same as, returnObject(). Also, the factory should be truly optional. it makes the class more flexible, without any sacrifice in functionality. the current implementation which allows construction of a GenericObjectPool without a factory, but throws NullPointerException when used, is broken. There's no way that can be considered robust code. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
