NOTE to community users:
This video contains examples for both WildFly 10.1 and the newly supported JBoss EAP 7.1.
For the cooperative examples "Client and server in different instances" the different Initial Context Factory class values shown for WildFly & JBoss EAP are because:
- 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 will still work short term but should not be relied on. If used the JBoss server.log will contain message:
"INFO [org.wildfly.naming] (com.ca.gen.smrt.ServletSession) WFNAM00025: org.jboss.naming.remote.client.InitialContextFactory is deprecated; new applications should use org.wildfly.naming.client.WildFlyInitialContextFactory instead"
CA Gen 8.6 remote EJB execution with WildFly 10.1 - CA Knowledge