[jbossts-issues] [Red Hat JIRA] (JBTM-3397) Ensure that LRA uses the features provided by ArjunaCore
by Michael Musgrove (Jira)
[ https://issues.redhat.com/browse/JBTM-3397?page=com.atlassian.jira.plugin... ]
Michael Musgrove edited comment on JBTM-3397 at 2/18/21 4:20 AM:
-----------------------------------------------------------------
The seven tasks mentioned in the description have now been merged.
There is still more that can be done with this JIRA but for now the primary goals have been met.
We can raise another JIRA after the next design review.
was (Author: mmusgrov):
The seven tasks mention in the description have now been merged.
There is still more that can be done with this JIRA but for now the primary goals have been achieved.
We can raise another JIRA after the next design review.
> Ensure that LRA uses the features provided by ArjunaCore
> --------------------------------------------------------
>
> Key: JBTM-3397
> URL: https://issues.redhat.com/browse/JBTM-3397
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: LRA
> Affects Versions: 5.10.6.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Major
>
> The narayana implementation of LRA does not follow some of the expectations of ArjunaCore:
> 1. Rename Transaction to LongRunningAction and extend BasicAction (it doesn't need anything from TwoPhaseCoordinator or AtomicAction) and make sure the type name matches the usual convention (ie it should follow the type hierarchy)
> 2. Do not override BasicAction#end
> 3. Remove the confusing comment in LRARecord#value()
> 4. Do not duplicate functionality of BasicAction#Current()
> 5. Do not duplicate StateManager.get_uid()
>
> There are two more changes that I will raise separate JIRAs for (and link them to this one):
> 6. Don't use RecordType.USER_DEF_FIRST0 for LRA participants
> 7. Use the support in ArjunaCore for managing nested LRAs.
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)