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=14982>. 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=14982 GenericObjectPool does not work with null factory. Summary: GenericObjectPool does not work with null factory. 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] The descriptions of the GenericObjectPool constructors state that factory may be "possibly null". This is a desirable feature, but its implementation is buggy and incomplete. The pool is unusable with null factory: it throws NullPointerException because _factory is never checked for null and there's no way to populate the pool; need addNewObject() method. For convenience there should be constructors that do not require passing factory at all. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
