1 of 1 people found this helpful
Depends on how your client code use the API.
How the client look like?
You can find some examples here jboss-as-quickstart/ejb-clients at ejb-clients might be out of date in some examples.
I suppose you need to have a look to the jboss-api sub-project.
Also you might use a hack and set a ThreadLocal inside the NodeSelector to control the behaviour for tests.
Thanks for your response,
The examples are interesting.
In fact, the context is a little bit more complex than I said precendtly.
Indeed, my JUnit test call a remote SBSL (called EjbTest for example) which has to call another remote SBSL (EjbBusiness).
The first SBSL can be comparated to a proxy which allows to get the "business SBSL".
Finally, I think the easier solution is to use two differents DeploymentNodeSelector implementations : one in production and the other in test environment.
The one used in test will be able to manage all cases thanks to a little hack
I just have to manage two jboss-ejb-client.xml files.