Can I refer you to the specifications. You will need to read them if you are attempting to bypass the spec defined assumptions/behaviours.
You will find lots to read.... :-) I will also repeat, your question is also off topic for the JMS forum. The basics are: JTA - java mapping of XA/Open describes one transaction manager model JTS - java mapping of OTS another transaction manager model J2EE - Overview of J2EE platform EJB - EJB programming model (read the part about transaction diamonds) To answer part of your question very quickly, but more accuratly than my original post: JTA can either be implemented directly or it can be a mapping on top of another TM implemetnation (e.g. JTS/OTS). OTS allows multiple active threads/transaction but also defines separate behaviour for a reconciliation stage of those threads before transaction commit. The JTA spec also allows this behaviour, but it also allows the opposite, i.e. only the originator thread can do work/commit the transaciton. The JTA spec does not define a reconcilation (leaving it to the TM implementation which is usually OTS underneath - but not in JBoss's case). Well actually it does implicitly in that it assumes a single thread of control (negating the need for a reconciliation). The EJB spec does not allow this behaviour (diamonds mentioned above) but recognises that the AS cannot detect every occurance of this pattern. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862770#3862770 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862770 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
