-
Requirement
-
Resolution: Done
-
Blocker
-
None
-
-
-
https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3512, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3544, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3654, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3753, https://gitlab.cee.redhat.com/red-hat-jboss-enterprise-application-platform-documentation/eap-documentation/merge_requests/3780
EJB Client Simplification recommendations based on legacy JBoss EAP 5.
- no need to know node names to get a transaction object
- i.e. context.lookup("UserTransaction") // or some other string
- automatic (configurable) transaction stickyness for EJB's (there are other issues about that)
- no need to know whether a client invoke a cluster
- cluster view should use the same properties as the connection and not add some duplicate cluster stuff
- autodiscovery for clusters
- simplify / unify the client configuration
- use the same approach for standalone and server-side clients
- is related to
-
JBEAP-12900 [7.1] Revisit Client Configuration for EJB/JNDI
- Closed
- relates to
-
JBEAP-11569 Elytron migration: new means to configure security properties in EJB client
- Closed
-
JBEAP-13837 Add diagrams illustrating how the new ejb lookup & failover works
- Closed