You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2002/12/01 16:40:45 UTC

DO NOT REPLY [Bug 14982] New: - GenericObjectPool does not work with null factory.

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: commons-dev@jakarta.apache.org
        ReportedBy: sschwell@yahoo.com


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:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>