Hello All,
We had some email discussion about this in the past as well but I think the key points are captured in the JIRA
https://java.net/jira/browse/JTA_SPEC-4 and so I'm starting this clean thread.
This is where I see we are now with open issues of functionality and implementation…
Functionality: Ordering is the crux of the feature, however, the extent and particulars of the ordering need to be determined and include:
- John Halliday's comment "At the risk of scope creep I'd welcome some discussion of more general approaches to communicating resource semantics, such that we can do variations on Last Resource Commit Optimization / Logging Last Resource, parallel prepare, etc"
- Perhaps related to this point I think we need to spec out aspects such as the precedence if more than one resource that is to be ordered first (or last) is enlisted in a given transaction, etc.
Implementation: How the functionality is provided by the application server and used by the application:
- XAResource extension
- Annotation
- resource-reference extension
Discuss… ;-)
Regards,
Paul