aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Cummins (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-845) Support unwrap and isWrappedFor functions with older JDBC drivers in ConnectionWrapper
Date Thu, 07 Jun 2012 21:50:24 GMT

     [ https://issues.apache.org/jira/browse/ARIES-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Holly Cummins resolved ARIES-845.
---------------------------------

    Resolution: Fixed
      Assignee: Holly Cummins

I've delivered a modified version of the patch which does the best it can to allow the transaction
wrapper to function on a Java 5 VM. I've disabled the animal sniffer tests where required
so that we can use the 1.0.0 parent pom.
                
> Support unwrap and isWrappedFor functions with older JDBC drivers in ConnectionWrapper
> --------------------------------------------------------------------------------------
>
>                 Key: ARIES-845
>                 URL: https://issues.apache.org/jira/browse/ARIES-845
>             Project: Aries
>          Issue Type: Improvement
>          Components: Transaction
>         Environment: JDK6
>            Reporter: Balazs Zsoldos
>            Assignee: Holly Cummins
>         Attachments: ConnectionWrapper.java.patch
>
>
> ConnectionWrapper now simply delegates the unwrap and isWrappedFor functions to the wrapped
connection. It would be good if we could be sure that the JDBC driver supports these functions
as it is written in the javadoc. However in postgres 9.1 or H2 these functions are not supported
and it is impossible to use api from that is supported by the vendor (e.g. LargeObject API
from Postgres).
> A possible solutions is:
> In these functions we check first if the wrapped connection implements the queried interface.
If not we delegate the function (thinking if we wrapped a wrapper it hopefully supports these
functions).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message