A Seam use reported an isssue in the way Hibernate register a sync with
JBossTM (the old one at least).
I've described the issue in JIRA
http://jira.jboss.com/jira/browse/EJBTHREE-540
Please provide feedbacks on this one. We must fix that before JBoss AS
4.0.4 / JBoss EJB3 / Hibernate
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
I guess the only way an OTS backed JTA impl
could implement the new stuff:
Adrian Brock wrote:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
Synchronizations were standardised first in the OTS. Prior to that
everyone did it in a vendor-specific manner.
I guess the only way an OTS
On Wed, 2006-04-26 at 15:03 +0100, Mark Little wrote:
Adrian Brock wrote:
I've closed the JTA issue:
http://jira.jboss.com/jira/browse/JBAS-3155
AFAIK, this originally comes from the OTS spec.
Synchronizations were standardised first in the OTS. Prior to that
everyone did it
Not sure what you mean. That reference is purely about registering a
subordinate synchronization with the original transaction coordinator.
JBossTS does this already because it's an optional part of the OTS
specification. You create and enlist the sub-synchronization with the
root
