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.

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.1 releases.

The following configurations must run without errors:

  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1 server
  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 7 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 6 server

The following configurations must run without errors:

  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1 server
  • Connecting from a JBoss EAP 8.1 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.1. 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.1 or a JBoss EAP 7 server
  • Connecting from a JBoss EAP 8.1 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.1 server
  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 7 server
  • Connecting from a JBoss EAP 8.1 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.1 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 7 server

JBoss EAP 8.1 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.1 client to a JBoss EAP 6 server
  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1 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.1 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 7 server

JBoss EAP 8.1 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 configurations are not compatible:

  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 6 server
  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1 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.1 server
  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 7 server
  • Connecting from a JBoss EAP 8.1 client to a JBoss EAP 6 server
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top