5 Replies Latest reply on Sep 9, 2009 9:00 AM by Tim Fox

    JCA adaptor dependant on the jboss transaction spi.

    Andy Taylor Master

      The jca handles its own transaction demarcation via the Transaction Manager. currently we get this by the following code

      tm = TransactionManagerLocator.locateTransactionManager();


      Unfortunately this doesn't work in JBoss 4.x since the its a later addition to the API. we could change it to the following

      tm = TransactionManagerLocator.getInstance().locate();


      which would fix it but this means that XA support would only work in other App servers if the transaction API was available.

      I'm not sure how best to resolve this issue and if we should. We could look it up from JNDI i guess?