[WFTC-13] LocalUserTransaction provide methods to set it's availability #13
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.
This is done because of local transaction invoked in scope of
@transactional interceptor
(e.g. from Narayana cdi implementation) needs to know if it's fine to
being invoked that context if not exception is thrown.
3.7 Transactional Annotation:
If an attempt is made to call any method of the UserTransaction
interface from within the scope of a bean or method annotated with
@transactional and a Transactional.TxType other than NOT_SUPPORTED or
NEVER, an IllegalStateException must be thrown.
LocalUserTransaction
setAvailability
/isAvailable
methods will be called through transactions spi from transaction Narayana cdi interceptor.