[
https://issues.redhat.com/browse/WFLY-14424?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on WFLY-14424:
--------------------------------------------
The server configurations are different (one has outbound connections, the other does not)
and setting up the two clusters is really simple in any case, so reuse would be minimal.
Part of the reason for creating this test case is to show in a simple way configuration of
two clusters and interaction of the EJB client with the the clusters, so keeping things
self-contained is an advantage.
Add EJB client test case for interacting with two non-overlapping
clusters
---------------------------------------------------------------------------
Key: WFLY-14424
URL:
https://issues.redhat.com/browse/WFLY-14424
Project: WildFly
Issue Type: Task
Components: Clustering
Affects Versions: 22.0.0.Final
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Priority: Major
Fix For: 23.0.0.Beta1
Write a test case which shows:
* how to configure two non-overlapping clusters
* how to specify the cluster affinity value which will be generated by the cluster for
use in topology updates
* the creation of EJB client proxies which can interact with those clusters via the
cluster specification
* creation of proxies using EJBClient API and JNDI lookup for both stateful and stateless
bean deployments
--
This message was sent by Atlassian Jira
(v8.13.1#813001)