JTA: branch qualifier

Question

          Seems to me WLS 7.0 TM thinks a transaction ID with the same transaction ID and
          different branch qualifier to be two different transactions, which is not compliant
          to JTA spec.
          According to JTA specification, '3.3.4 Transaction Equality and Hash Code'
          section, "The Transaction equals method should return true if the target
          object and the parameter object both refer to the SAME GLOBAL TRANSACTION";
          In section '3.3.1 Resource Enlistment' section, it states " If the XAResource
          object represents a resource manager who has not previously seen the global
          transaction, the TM establishes a different transaction branch ID1 and Java
          Transaction API ensures that this new resource manager is informed about the
          transaction completion with proper prepare-commit calls".
          Therefore, it is a quite common case that new branches of a same global
          transaction are created in a distributed transaction. Therefore identifying
          transaction IDs with same global transaction ID but different branch qualifier
          as the same global transaction, should be a normal practice. For example,
          Oracle database server will always combines the database work performed in
          different branches of the same global transaction in one commit of any of the
          branches. At the same time, treating these brances as the same transaction also
          has the benefit of simplifying transaction recovery at times of crash.
          Is there a plan for WLS to follow the JTA spec in this aspect, if it is true?
          Thanks,
          -Zhijiang
          

Answer 1

Hi Vinay,
1. Does this mean you want to create one qualified record whenever main table record gets created? If yes, i dont this is possible and i can think of two reasons
- We cannot assign value to Qualified table field unless there is a association between main table record and qualified table record and this association cannot be created dynamically.
- We cannot run assignments on Qualified table fields
2. Yes, it is mandatory to have Taxonomy table and lookup field to create Assignment Branch
Regards,
Jitesh Talreja