Continuation of discussion started at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=95058. This takes on new urgency due to the use of JBossTS in AS 4.2 (http://jira.jboss.com/jira/browse/JBAS-3892). I hadn't realized that was the plan until today. Basically, we need to come up with a solution for this in a matter of weeks. A solution most likely involves either a new JBC release or a new Hibernate release. I'll paste some earlier comments included in a discussion on the jbosscache-dev list: "Brian Stansberry" wrote : | Anyone have any good thoughts on what to do about it? Perhaps Hibernate exposes something like JBC's OrderedSynchronizationHandler, which the JBC integration can use to insert it's synchronization at the correct point? | "Manik Surtani" wrote : Not sure, cc'ing Hibernate-all. Even if there was such an ordered sync handler, we'd have to expose a mechanism to have this injected. Perhaps via the Runtime. "Emmanuel Bernard" wrote : | No, not possible right now. | | This problem roots to JTA, we really should push the ability to: | 1. guaranty synchronization ordering | 2. query/alter the synchronization list | in a standard way. | | 1. is not possible today and | javax/transaction/TransactionSynchronizationRegistry is way too limited 2. is useful when writing frameworks on top of JavaEE as a way to keep state / avoid multiple synchronization on a per transaction basis. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993541#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...