Support for XA data sources

[hoyacom]

Support for XA data sources

[GoogleCodeExporter]

Indeed, a way to solve your issue could be to create a "XADataSourceSpy", and 
also a "XAConnectionSpy", but the problem is: should we provide support only 
for the method "PooledConnection#getConnection()" (that could be wrapped easily 
by a ConnectionSpy)? I don't really see the point for a XA resource. 

Providing a full support for XADataSources would be a completely new branch of 
log4jdbc, we would need to create "ConnectionEventListenerSpy", 
"StatementEventListenerSpy", "XAResourceSpy", etc. 

If you wanted to provide such a patch, I could consider it. 

Original comment by [email protected] on 21 Mar 2014 at 12:34

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

As a workaround, I've also found that my JTA transaction manager (Atomikos) has 
a datasource bean that can be used to wrap the XA datasources and thus provide 
the regular datasource interface that can be further wrapped by DataSourceSpy.  
e.g.:

    <!-- Atomikos's XA capable pooling data source. -->
    <bean id="myJTADataSource" class="com.atomikos.jdbc.AtomikosDataSourceBean">
        <property name="xaDataSource" ref="myh2XaDataSource" />
        <property name="uniqueResourceName" value="myDatabase" />
                ...
    </bean>

    <!-- Special logging wrapper for our data source that spys on JDBC calls -->
    <bean id="myJTADataSourceSpied" class="net.sf.log4jdbc.sql.jdbcapi.DataSourceSpy">
        <constructor-arg ref="myJTADataSource" />
    </bean>

I have to believe this approach is readily available for almost any JTA 
transaction manager that uses XA data sources.  IMO you can close this issue as 
won't fix because, as you said, its a lot of work to support XA natively and 
I'm not convinced now that there would be any benefit.

Original comment by [email protected] on 24 Mar 2014 at 2:37

[GoogleCodeExporter]

Thanks for the update. Won't fix :)

Original comment by [email protected] on 25 Mar 2014 at 1:47

• Changed state: WontFix