[jboss-jira] [JBoss JIRA] (WFLY-13126) jboss-ejb-client affinity refactor
Cheng Fang (Jira)
issues at jboss.org
Tue Feb 18 13:19:00 EST 2020
[ https://issues.redhat.com/browse/WFLY-13126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Fang moved EAP7-1450 to WFLY-13126:
-----------------------------------------
Project: WildFly (was: JBoss EAP Planning for version 7 and above)
Key: WFLY-13126 (was: EAP7-1450)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: EJB
(was: EJB)
EAP PT Pre-Checked (PC): (was: TODO)
Target Release: (was: 7.4.0.GA)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
EAP PT Analysis Document (AD): (was: TODO)
> jboss-ejb-client affinity refactor
> ----------------------------------
>
> Key: WFLY-13126
> URL: https://issues.redhat.com/browse/WFLY-13126
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: EAP-CD20
>
> Refactor of jboss-ejb-client internal operation: change the way in which proxy affinity (an object that decides on which node invocation should be performed) is determined. Instead of calculating it on client side we would let server set the affinity when necessary and propagate it to the client.
> This refactor is supposed to reduce the complexity of jboss-ejb-client code and as a result, make it significantly easier to maintain. Richard has prepared a comprehensive document describing the suggested modifications: https://mojo.redhat.com/docs/DOC-1204767
> Parallelly, the test suite has to be refactored to make it compatible with the new algorithm and to provide broad coverage of jboss-ejb-client operation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list