This area currently under discussion in JSR-107.
https://github.com/jsr107/jsr107spec/issues/16
Perhaps you should raise this on the same issue as a related config issue?
I'm happy with the above regarding the config changes.
On 12 Sep 2011, at 10:40, Mircea Markus wrote:
Hi,
ATM a cache is marked as transactional by setting the transactionalManagerLookup,
transactionalManagerLookupClass or enable batching.
This is a bit hard to explain/clumsy and also doesn't work well with the xml config:
if one wants the default cache to be transactional and a named cache not to be, it would
have to specify an empty transactionManagerLookup attribute - not nice.
So an alternative would be to have an explicit "isTransactional"
configuration.
One way to do it is to add a "mode" attribute under the transactional element:
<transaction mode="NON_TRANSACTIONAL | TRANSACTIONAL_SYNCHRONIZED |
TRANSACTIONAL_FULL_XA | TRANSACTIONAL_XA_NO_RECOVERY" />
Somehow similar to the clustering element's mode attribute.
Pete is there an JSR-107 for the above enum? I looked for it in both the spec and API but
couldn't find one...
How does this sound?
Cheers,
Mircea
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev