[JBTM-2853][JBTM-2858][JBEAP-8890] fix for not working txn xts/rts bridging #9782
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Webservices module needs to depend on wfly txn client now
ochaloup
force-pushed
the
JBTM-2853-JBTM-2858-xts-handler-rts-filter
branch
from
0e67c82
to
0f1742f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding XTS WS handler and RTS rest provider which hook after transaction is imported by TXN bridge to Narayana. This hooks then cause that the transaction from Narayana is pulled by wildfly transaction client to its global context. Wildfly transaction client is then capable to work with the transaction and used it for example for EJB interceptor processing.
https://issues.jboss.org/browse/JBTM-2858
https://issues.jboss.org/browse/JBTM-2853
https://issues.jboss.org/browse/JBEAP-8890
eap7x: https://github.com/jbossas/jboss-eap7/pull/1485