CA Gen 8.6 remote EJB execution with WildFly 10.1 & JBoss EAP 7.1 and "Initial Factory Class"


Article ID: 125067


Updated On:


CA Gen CA Gen - Workstation Toolset CA Gen - Host Encyclopedia CA Gen - Run Time Distributed


CA Gen 8.6 supports WildFly 10.1 & JBoss EAP 7.1 with required PTFs installed.

When a Gen Web client is installed on one instance of an Application Server and the Gen EJB server is installed on a second of an Application Server the transaction routing needs to include the "{Initial Factory Class}" to enable the remote EJB to be loaded successfully.


CA Gen 8.6
WildFly 10.1
JBoss EAP 7.1


Although JBoss EAP uses the WildFly core it should be noted that WildFly 10.1 and JBoss EAP 7.1 use different values for"{Initial Factory Class}"

WildFly 10.1 (WildFly Core 2.0.10.Final) still uses the older org.jboss.naming.remote.client.InitialContextFactory  

JBoss EAP 7.1 (WildFly Core 3.0.10.Final-redhat-1) uses the new org.wildfly.naming.client.WildFlyInitialContextFactory.
In the later WildFly Core version 3.0.10 used by JBoss EAP 7.1 org.jboss.naming.remote.client.InitialContextFactory is deprecated so in the short term it will still work but should not be relied upon long term. If it is used the JBoss server.log will contain message: 
"INFO  [org.wildfly.naming] ( WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead

Additional Information

CA Gen 8.6 docops 
Distributed Processing > Working With Distributed Processing > Overriding Communications Support at Execution Time > Comm Config Files
See link for ""

CA Gen EDGE Community
"Video Released on Generating Web View Applications":