WFLY-2137 Fix circular dependency between security subsystem, jacorb …

[stuartwdouglas]

…and the transaction subsystem when JTS is enabled

[wildfly-ci]

Linux Build 7514 is now running using a merge of 795c329

[wildfly-ci]

Linux Build 7516 is now running using a merge of 795c329

[wildfly-ci]

Linux Build 7518 is now running using a merge of 795c329

[wildfly-ci]

Linux Build 7520 is now running using a merge of 795c329

[wildfly-ci]

Linux Build 7522 is now running using a merge of 795c329

[wildfly-ci]

Linux Build 7524 is now running using a merge of 720fe87

[wildfly-ci]

Linux Build 7524 outcome was SUCCESS using a merge of 720fe87
Summary: Tests passed: 3103, ignored: 369 Build time: 00:49:05

[bstansberry]

I had similar transaction capability stuff in a branch (https://github.com/bstansberry/wildfly/commits/use-cap-req) but then never moved it forward once I realized the contract of these capabilities was really unclear. Other subsystems depend on a variety of different transactions stuff, so we need to work out what the API is. Some of the stuff people use is spec classes, while some is Arjuna details.

The other reason I didn't move forward is the way jts works violates what's described at http://lists.jboss.org/pipermail/wildfly-dev/2015-July/004269.html. I vaguely figured there that we'd add a child resource with the existing attribute retained for compatibility. (In a read the attribute would basically just indicate whether the child resource exists; in a write it would trigger add/remove of the child resource.)

Sounds like it's time to get this sorted.

[bstansberry]

How about this?

1. Drop the org.wildfly.transactions.jts part. Unless I missed it, it's not used in this PR.
2. The rest is fine. You're not actually using any contract from the org.wildfly.transactions capability. You still directly use the subsystem's service name. So all this does is commit us to having a capability called "org.wildfly.transactions", and that is pretty safe. If we later create child capabilities for accessing services, or have "org.wildfly.transactions" itself provide something, that won't be an incompatible change.

This lets this specific problem be fixed ASAP without prematurely committing to much.

[wildfly-ci]

Linux Build 7541 is now running using a merge of 9802d27

[wildfly-ci]

Linux Build 7541 outcome was SUCCESS using a merge of 9802d27
Summary: Tests passed: 3110, ignored: 365 Build time: 00:51:00