[ https://issues.jboss.org/browse/JBTM-2259?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2259: ----------------------------------- OK, but this is not compliant with the standards and therefore if some other transaction engine is used it will break. The reason ordering of resources and synchronisations isn't supported in the standards is because it becomes very hard to manage global ordering in a heterogenous environment. Are we really happy to add something which basically ties IronJacamar and Narayana together? I'm no so sure. While it's nice to add something like resource ordering, as we do with AbstractRecords, it should be done cautiously, in situations where no other option is possible, or as an optimisation, i.e., so without it the system still works, but may be slower, less efficient etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)