Appendix A. Reference material As a user of JBoss EAP, you can expect seamless compatibility and interoperability between different releases. Connecting from various clients to servers is supported, with only specific cases requiring additional considerations. A.1. Compatibility and interoperability between releases This section describes the compatibility and interoperability of client and server enterprise beans and messaging components between the JBoss EAP 6, JBoss EAP 7, and JBoss EAP 8.0 releases. A.1.1. Enterprise beans remoting over Internet Inter-ORB Protocol The following configurations must run without errors: Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 6 server A.1.2. Enterprise beans remoting using Java Naming and Directory Interface The following configurations must run without errors: Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server JBoss EAP 6 provided support for the Enterprise Beans 3.1 specification and introduced the use of standardized global Java Naming and Directory Interface namespaces, which are still used in JBoss EAP 8.0. The changes in Java Naming and Directory Interface namespace names do not introduce incompatibilities for the following configurations: Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 or a JBoss EAP 7 server Connecting from a JBoss EAP 8.0 or JBoss EAP 7 client to a JBoss EAP 6 server A.1.3. Enterprise beans remoting using @WebService The following configurations must run without errors: Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 6 server A.1.4. Messaging standalone client The following configurations must run without errors: Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server JBoss EAP 8.0 built-in messaging is not able to connect to HornetQ 2.3.x that shipped with JBoss EAP 6 due to protocol compatibility issues. For this reason, the following configuration are not compatible: Connecting from a JBoss EAP 8.0 client to a JBoss EAP 6 server Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 server Note To make this connection possible, you must create a legacy connection factory, accessible through Java Naming and Directory Interface. A.1.5. Messaging MDBs The following configurations must run without errors: Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server JBoss EAP 8.0 built-in messaging is not able to connect to HornetQ 2.3.x that shipped with JBoss EAP 6 due to protocol compatibility issues. For this reason, the following configuration are not compatible: Connecting from a JBoss EAP 8.0 client to a JBoss EAP 6 server Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 server Note To make this connection possible, you must create a legacy connection factory, accessible through Java Naming and Directory Interface. A.1.6. Messaging bridges The following configurations must run without errors: Connecting from a JBoss EAP 6 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 7 client to a JBoss EAP 8.0 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 7 server Connecting from a JBoss EAP 8.0 client to a JBoss EAP 6 server

Commands: