Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

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

The following configurations must run without errors:

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

A.1.3. Enterprise beans remoting using @WebService
Copy link

The following configurations must run without errors:

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

A.1.4. Messaging standalone client
Copy link

The following configurations must run without errors:

  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1-beta server
  • Connecting from a JBoss EAP 8.1-beta client to a JBoss EAP 7 server

JBoss EAP 8.1-beta 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-beta client to a JBoss EAP 6 server

  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1-beta 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
Copy link

The following configurations must run without errors:

  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1-beta server
  • Connecting from a JBoss EAP 8.1-beta client to a JBoss EAP 7 server

JBoss EAP 8.1-beta 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-beta client to a JBoss EAP 6 server

  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1-beta 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
Copy link

The following configurations must run without errors:

  • Connecting from a JBoss EAP 6 client to a JBoss EAP 8.1-beta server
  • Connecting from a JBoss EAP 7 client to a JBoss EAP 8.1-beta server
  • Connecting from a JBoss EAP 8.1-beta client to a JBoss EAP 7 server
  • Connecting from a JBoss EAP 8.1-beta client to a JBoss EAP 6 server
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

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

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

Theme

© 2025 Red Hat