Deprecated in Red Hat JBoss Enterprise Application Platform (EAP) 7

Updated

Deprecated features will not see additional feature development in future versions of EAP, and may not be present in EAP 8. This list of deprecations reflects the currently known list of deprecations and will be updated as new deprecations are made.

JDK

  • JDK 8 is deprecated, EAP 8.0 will implement JakartaEE 10 which will require JDK11
  • JDK 11 - In future JBoss EAP releases, Java SE requirements will be reevaluated based on the industry (for example, Jakarta EE 10+, MicroProfile and so on) and market needs.

JSVC

  • JSVC on RHEL is deprecated in EAP 7 and will be removed in EAP 8.0
    Although Jsvc works on RHEL, we strongly recommend that you use the native methods for running JBoss EAP as a service on RHEL.

Security

Legacy security subsystem (PicketBox)

  • The 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 Elytron subsystem.
  • The PicketBox-based security vault, including access by using the legacy security subsystem and the core-service=vault kernel management resources, is now deprecated in this release.
  • application-security-domain resources - The application-security-domain resources in ejb3 and undertow subsystems are deprecated. These will no longer be needed in EAP 8 as Picketbox will be removed and there will only be the Elytron security configuration.
  • The org.wildfly.extension.picketlink extension, and the picketlink-federation and picketlink-identity-management subsystems this extension supports, are now deprecated. Migrate your single sign-on implementation to Red Hat Single Sign-On.

Salted Challenge Response Authentication Mechanism

  • The following Salted Challenge Response Authentication Mechanisms (SCRAMs) and their channel-binding variants are deprecated:

    • SCRAM-SHA-512
    • SCRAM-SHA-384

Hibernate

  • Hibernate Criteria has been deprecated for some time and will no longer exist in EAP 8.0, applications using Hibernate Criteria would need to switch and use JPA Criteria
  • Hibernate Search 5 APIs Deprecated in JBoss EAP 7.4
  • The Hibernate ORM 5.1 native API bytecode transformer has always been deprecated since it was originally introduced.
  • Hibernate started defaulting to use Byte Buddy instead of javassist in EAP 7.2. Hibernate 5.6 dropped support for javassist and EAP 8+ will no longer include javassist as such.

Clustering

  • The following resources in the clustering subsystems are deprecated:

The infinispan subsystem

/subsystem=infinispan/remote-cache-container=*/component=transaction
/subsystem=infinispan/remote-cache-container=*/near-cache=*

The jgroups subsystem

/subsystem=jgroups/stack=*/protocol=S3_PING
/subsystem=jgroups/stack=*/protocol=GOOGLE_PING

EJB

  • jboss-ejb-client.properties - is deprecated, standalone client applications should use wildfly-config.xml as shown here , client applications running in EAP should use jboss-ejb-client.xml
  • jboss-ejb-client-legacy.jar - is legacy and deprecated, client applications should configure the InitialContext as shown here, this deprecated includes these classes which are in the jboss-ejb-client-legacy.jar as well as the org.jboss.eap.wildfly-ejb-client-legacy-bom Maven BOM, see more details:
    • org.jboss.ejb.client.ContextSelector
    • org.jboss.ejb.client.EJBClientConfiguration
    • org.jboss.ejb.client.PropertiesBasedEJBClientConfiguration
    • org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector
    • org.jboss.ejb.client.EJBClientContext.setSelector(...)
  • EJB Client Scoped Context is deprecated and client applications should configure the InitialContext as shown here, this deprecation includes properties such as this which are passed into the InitialContext:
    • remote.connections
    • remote.connection.*
    • org.jboss.ejb.client.scoped.context

Naming

  • Remote Naming (org.jboss.naming.remote.client.InitialContextFactory) has been deprecated since EAP 7.1 , org.wildfly.naming.client.WildFlyInitialContextFactory should be used instead.
    • Deployments depending on the org.jboss.remote-naming module should depend on the org.wildfly.naming-client instead.
  • The legacy 'remote:' remoting protocol is only used for EAP 6, EAP 8 clients / servers should use the default remote+http / remote+https.

EAP Configurations

Domain Mode

  • 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 (standalone.xml, host.xml, and 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.

Images

  • Jolokia support including env properties
  • Prometheus support including env properties
  • GALLEON_PROVISION_DEFAULT_FAT_SERVER env property (that was used in OpenShift templates), is not longer used, use GALLEON_PROVISION_LAYERS cloud-default-config for EAP 8 images instead.
  • JBoss EAP templates for OpenShift are deprecated.
    • eap74-beta-starter-s2i.json and eap73-third-party-db-s2i.json templates
    • The eap74-beta-starter-s2i.json and eap74-beta-third-party-db-s2i.json templates are deprecated and are removed in JBoss EAP 7.4.0.GA.
  • The RHSSO Galleon Layer is deprecated in JBoss EAP 7.4
  • OpenShift Container Platform (OCP) 3.11 is deprecated for JBoss EAP 7.4.
  • EAP 7 / OpenJDK 11 Images - OpenJDK 11 will be end of life in October 2024, update to EAP 7 / OpenJDK 17 prior to then to keep up to date on security CVEs / bug fixes see more details here.
  • EAP 7.4 / OpenJDK 8 / RHEL 7 Containers deprecated as RHEL 7 goes end of life before EAP 7.4. An EAP 7.4 / OpenJDK 8 / RHEL 8 container will replace it.

OpenJ9 images for IBM Z and IBM Power Systems will be deprecated. The following OpenJDK11 Builder and Runtime images have been updated to support multiple architectures:

  • jboss-eap-7/eap74-openjdk11-openshift-rhel8 (Builder image)
  • jboss-eap-7/eap74-openjdk11-runtime-openshift-rhel8 (Runtime image)
    You can use the OpenJDK11 images with the following architectures:
  • x86 (x86_64)
  • s390x (IBM Z)
  • ppc64le (IBM Power Systems)
    If you want to use the OpenJ9 Java Virtual Machine (JVM) with the OpenJDK11 images, see Java Change in Power and Z OpenShift Images.

OpenShift Online

As per the OpenShift Online Life Cycle, OpenShift 3.11's Maintenance Support Phase ended in June 2023. OpenShift Online is presently not accepting any new subscribers and existing subscribers were informed about the upcoming platform decommissioning.

Logging

Maven Bill of Materials (BOMs)

  • EAP BOMs - The existing BOMs are deprecated with a view to providing BOMs (perhaps including some of the existing ones) relevant to the functionality in the next major version of JBoss EAP.
  • Spring BOM : jboss-eap-jakartaee8-with-spring4 is deprecated
    • Although Red Hat tests that Spring applications run on Red Hat JBoss Enterprise Application Platform 7.4, 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 7.4.

Testing

JDK

  • IBM JDK
  • Eclipse OpenJ9

Operating systems

Although support for these platforms was deprecated in a previous JBoss EAP release, some artifacts and resources linked to these platforms were not removed, such as the wildfly-openssl native library binding . For Red Hat JBoss Enterprise Application Platform 7.4, those artifacts and resources have been removed.

  • Microsoft Windows Server on i686
  • Red Hat Enterprise Linux (RHEL) 6 on i686

JMS Providers

Installer

  • The current jboss-eap-7.y.0-installer.jar is deprecated and will be replaced by a new installer in EAP 8.0.
    • The shortcut creation is deprecated
    • The interactive console installation mode is deprecated

Mod Cluster

  • The modcluster subsystem deprecated the 'connector' attribute on the proxy element and replaced it with 'listener' to avoid confusion. The management schema in EAP 7.4 was already using the updated 'listener', but it was still possible to set the 'connector' attribute as well. In EAP 8.0 this deprecated 'connector' attribute will be removed and the 'listener' attribute will have to be used.

JAXP

  • The Apache Xerces and Apache Xalan JBoss Modules will be removed and JAXP will be provided by the JDK. Applications or custom JBoss Modules explicitly depending on org.apache.xerces or org.apache.xalan will need to remove these dependencies and declare a dependency on java.xml when migrating to EAP 8.0.

Other

  • Agroal subsystem - The datasources-agroal subsystem is deprecated.
  • Codehaus Jackson - The Codehaus Jackson 1.x module, which is currently unsupported, is deprecated in JBoss EAP 7.4.
  • JBoss EAP Server Side JavaScript support - Previously, JBoss EAP Server Side JavaScript support was offered as a Technology Preview. It is now deprecated in this release. Note: In JDK11 the Nashorn JavaScript Engine was deprecated as per Content from openjdk.org is not included.JEP 335 and then removed in JDK15 as per Content from openjdk.org is not included.JEP 372, so the JavaScript Engine is no longer available in the JDK as per JDK15+.

References:

3.2. Deprecated features

SBR
Product(s)
Category
Components
Tags
Article Type