Our application consist of a total of 42 EAR components and several WAR components.
When a developer wants to test his changes for a component, than only that component is deployed on his local Wildfly instance.
The idea is that when other components, which are not deployed on his local Wildfly instance, need to be accessed, a remote Wildfly instance is used. This is the case for EJBs
In Wildfly 9, we used the following configuration:
The code for an EAR component has a jboss-ejb-client.xml with the following structure:
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
<remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" username="ejb" security-realm="ejb-security-realm">
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
<remote-destination host="DMP_MO_URL" port="8080"/>
The setup above was enough to make sure that if an EAR-component is not deployed locally, that the remote Wildfly instance would be used.
I've tried the following links the make it work for Wildfly 12 but it was unsuccessful:
Default it seems that the local Wildfly instance is used, but if never accesses the remote Wildfly instance if the local component is not found.
For now we implement the interface DeploymentNodeSelector and changed the jboss-ejb-client.xml configuration to the following:
<cluster name="ejb" username="ejb" security-realm="ejb-security-realm">
<property name="org.xnio.Options.SASL_POLICY_NOANONYMOUS" value="true"/>
<property name="org.xnio.Options.SSL_ENABLED" value="false"/>
How can I make it work on Wildfly 12, preferably by using the new configuration files?