[jboss-jira] [JBoss JIRA] (WFLY-11645) A way to prevent automatic changes of affinity when invoking clustered beans

[Brian Stansberry (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved JBEAP-13233 to WFLY-11645:
-------------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-11645  (was: JBEAP-13233)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                       EJB
                           (was: Clustering)
                           (was: EJB)
       Target Release:   (was: 7.1.0.GA)
    Affects Version/s:     (was: 7.1.0.CR2)


> A way to prevent automatic changes of affinity when invoking clustered beans
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-11645
>                 URL: https://issues.jboss.org/browse/WFLY-11645
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering, EJB
>            Reporter: Jan Martiska
>            Assignee: Jason Greene
>            Priority: Major
>
> When invoking a clustered bean, a user might want to set an affinity so that the invocations go to a particular node. This is done via EJB client APIs:
> {noformat}
> EJBClient.setStrongAffinity(beanProxy, new NodeAffinity("node1"));
> {noformat}
> however, if the bean is clustered, after each invocation, the affinity is automatically reset to a ClusterAffinity. So the user would have to apply this again before each invocation. There should be a way to tell EJB client to not do this.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)