Chapter 3. Unsupported features and deprecated features
3.1. Unsupported features
Support for some technologies is removed due to the high maintenance cost, low community interest, and better alternative solutions. The following features are not supported in JBoss EAP XP 3.0.0:
Platforms and features
JBoss EAP deprecated the following platforms in version 7.1. These platforms are not tested in JBoss EAP 7.4.
- Oracle Solaris on x86_64
- Oracle Solaris on SPARCv9
JBoss EAP 7.4 does not include the WildFly SSL natives for these platforms. As a result, SSL operations in Oracle Solaris platforms might be slower than they were on previous versions of JBoss EAP.
OpenJDK 8 image and image streams
Beginning with version 3.0, JBoss EAP XP no longer provides or supports OpenJDK 8 images or image streams.
RESTEasy provides a Servlet 3.0
ServletContainerInitializer integration interface that performs an automatic scan of resources and providers for a servlet. Containers can use this integration interface to start an application. Therefore, use of the following RESTEasy parameters is no longer supported:
Red Hat JBoss Operations Network
Using Red Hat JBoss Operations Network (JON) for JBoss EAP management is deprecated since JBoss EAP version 7.2. For JBoss EAP 7.4, support for Red Hat JON for JBoss EAP management is deprecated.
MS SQL Server 2017
MS SQL Server 2017 is not supported in JBoss EAP 7.4.
For a complete list of unsupported features in JBoss EAP 7.4, see the Unsupported features section in JBoss EAP 7.4 Release Notes.
3.2. Deprecated features
Some features have been deprecated with this release. This means that no enhancements are made to these features, and they might be removed in the future, usually the next major release.
Red Hat continues to provide full support and bug fixes under our standard support terms and conditions. For more information about the Red Hat support policy for JBoss EAP XP, see the Red Hat JBoss Enterprise Application Platform expansion pack life cycle and support policies located on the Red Hat Customer Portal.
jms-activemq decorator layer is deprecated, and this layer has been replaced with the
- Microsoft Windows Server on i686
- Red Hat Enterprise Linux (RHEL) 6 on i686
Databases and database connectors
- IBM DB2 11.1
- PostgreSQL / EnterpriseDB 11
- MariaDB 10.1
- MS SQL 2017
Lightweight Directory Access Protocol (LDAP) servers
- Red Hat Directory Server 10.0
- Red Hat Directory Server 10.1
The following Spring BOM that is located in the Red Hat Maven repository is now deprecated:
Although Red Hat tests that Spring applications run on JBoss EAP XP 3.0.0, you must use the latest version of the Spring Framework and its BOMs (for example,
x.y.z.RELEASE) for developing your applications on JBoss EAP XP 3.0.0.
For more information about versions of the Spring Framework, see Spring Framework Versions on GitHub.
Java Development Kits
- Java Development Kit 8 (JDK 8)
Java Development Kit 11 (JDK 11)
In future major JBoss EAP releases, Java SE requirements will be reevaluated based on the industry (for example, Jakarta EE, MicroProfile and so on) and market needs.
JBoss EAP OpenShift templates
JBoss EAP templates for OpenShift are deprecated.
eap-xp2-third-party-db-s2i.json template is deprecated and removed in JBoss EAP XP 3.0.0.
eap74-beta-third-party-db-s2i.json templates are deprecated and are removed in JBoss EAP 7.4.0.
Legacy security subsystem
org.jboss.as.security extension and the legacy
security subsystem it supports are now deprecated. Migrate your security implementations from the
security subsystem to the
org.wildfly.extension.picketlink extension, and the
picketlink-identity-management subsystems this extension supports, are now deprecated. Migrate your single sign-on implementation to Red Hat Single Sign-On.
PicketBox-based security vault
PicketBox-based security vault, both through the legacy security subsystem and the
core-service=vault kernel management resources is deprecated.
Managed domain support for previous versions of JBoss EAP
Support for hosts running JBoss EAP 7.3 and earlier versions in a JBoss EAP 7.4 managed domain is deprecated. Migrate the hosts in your managed domains to JBoss EAP 7.4.
Server configuration files using namespaces from JBoss EAP 7.3 and earlier
Using server configuration files (
domain.xml) that include namespaces from JBoss EAP 7.3 and earlier is deprecated in this release. Update your server configuration files to use JBoss EAP 7.4 namespaces.
The Agroal subsystem is deprecated.
application-security-domain resources in
undertow subsystems are deprecated.
Resources in the clustering subsystems
The following resources in the clustering subsystems are deprecated:
The Codehaus Jackson 1.x module, which is currently unsupported, is deprecated in JBoss EAP 7.4.
The following SCRAM mechanisms and their channel-binding variants are deprecated:
Hibernate ORM 5.1
The Hibernate ORM 5.1 native API bytecode transformer has always been deprecated since it was originally introduced.
The HornetQ client module is deprecated.
For a complete list of functionalities deprecated in JBoss EAP 7.4, see the Deprecated features section in JBoss EAP 7.4 Release Notes.