We wanted much more control over the JDBC statements we issue and wanted a light weight jdbc framework. So we have gone ahead and already started implementing our code with spring JDBC.

Now we are looking for a solution wherein we can commit into teh database and cache in a single transaction ? Is this possible with any transaction manager provided by jboss/spring ?

Its a clustered environment. Ans we are looking for a distributed cache.

Thanks a lot for such quick response

If I get ur response right,

First of my usecases can be achived by writing some custom code from my side, which gives me flexibility of fetching from database and then updating  the cache.Subsequent reads will take from cache.

My second usecase when i do a write into database and cache I need a transactional behaviour.  Is this also possible?

Is so which is the transaction manager i can use for mainting transactions across my database(spring jdbc) and  infinispan ?

Thanks a lot for all the replies. I will have a look at JBossTM and publish my finding once i get transaction working across spring jdbc and infinispan.

I started using atomikos transaction manager. I am able to get transaction with teh datasource but when trying to test the behaviour across  infinispan i get a exception.

java.lang.ClassCastException: com.atomikos.icatch.jta.UserTransactionManager cannot be cast to org.infinispan.transaction.lookup.TransactionManagerLookup

    at org.infinispan.factories.TransactionManagerFactory.construct(TransactionManagerFactory.java:48)

    at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:315)

    at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:251)

    at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:840)

This is what i have in teh default section of my cache config file.

   <default>

      <jmxStatistics enabled="true"/>

      <clustering mode="replication">

         <stateRetrieval

            timeout="20000"

            fetchInMemoryState="false"

            alwaysProvideInMemoryState="false"

         />

         <sync replTimeout="20000"/>

      </clustering>

       <transaction 

            transactionManagerLookupClass="com.atomikos.icatch.jta.UserTransactionManager"

            syncRollbackPhase="false"

            syncCommitPhase="false"

      useEagerLocking="false"/>

  </default>

i just decompiled teh source to check the code

      if (this.configuration.getTransactionManagerLookupClass() != null) {

        lookup = (TransactionManagerLookup)Util.getInstance(this.configuration.getTransactionManagerLookupClass());

      }

    }

I get a feel that there is a casting done to org.infinispan.transaction.lookup.TransactionManagerLookup. Isnt this a bug ?

Since it says  "Any JTA compliant transaction manager can be used."  How can we expect a JTA compaint transaction manager to implement infinispan specific interface ?

Thanks , my mistake . I totally misunderstood the attribute property.

I have now writen my own look up class which gets teh spring container instantiated transaction manager(atomikos) and it works fine.

Thanks again for such quick reply.