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 2003/09/14 00:42:56 UTC

DO NOT REPLY [Bug 23138] - getDelegate no longer useful since v1.7 of PoolingDataSource

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=23138>.
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=23138

getDelegate no longer useful since v1.7 of PoolingDataSource

dirk.verbeeck@pandora.be changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From dirk.verbeeck@pandora.be  2003-09-13 22:42 -------
Restored the getDelegate feature (access to the underlying connection)
If you set the "accessToUnderlyingConnectionAllowed" property to true then you
can do the following:

    Connection conn = ds.getConnection();
    Connection dconn = ((DelegatingConnection) conn).getInnermostDelegate();
    ...
    conn.close()

Default is false, it is a potential dangerous operation and misbehaving programs
can do harmfull things. (closing the underlying or continue using it when the
guarded connection is already closed)
Be carefull and only use when you need direct access to driver specific extentions.