Chapter 4. Unsupported, deprecated, and removed functionality
4.1. Unsupported features Copy linkLink copied to clipboard!
The following features are not supported by Red Hat.
4.1.1. Bootable JAR on OpenShift Copy linkLink copied to clipboard!
Bootable JAR on OpenShift is not supported for JBoss EAP 8.1. Instead, you can use the content trimming capability for deployment runtime in JBoss EAP for OpenShift.
For more information, see Capability trimming in JBoss EAP for OpenShift in Using JBoss EAP on OpenShift Container Platform.
4.2. Deprecated features Copy linkLink copied to clipboard!
Some features are deprecated with this release. This means that no enhancements will be made to these features, and they might be removed in a future release. For more information, see Deprecated in Red Hat JBoss Enterprise Application Platform (EAP) 8.
Red Hat will continue providing full support and bug fixes under our standard support terms and conditions. For more information about the Red Hat support policy, see the Red Hat JBoss Middleware Product Update and Support Policy located on the Red Hat Customer Portal.
The following features are deprecated:
4.2.1. read-config-as-xml operation Copy linkLink copied to clipboard!
The read-config-as-xml operation has been deprecated in JBoss EAP 8.1. Use the read-config-as-xml-file operation instead. For more information, see New operation to export server configuration as a stream.
4.2.2. Java 11 Copy linkLink copied to clipboard!
Java 11 has been deprecated and support ends with JBoss EAP 8.1.
4.2.3. OpenShift OpenJDK 17 images Copy linkLink copied to clipboard!
OpenShift OpenJDK 17 images are deprecated with JBoss EAP 8.1 and will be removed in an upcoming JBoss EAP 8.2 minor release.
4.3. Removed features Copy linkLink copied to clipboard!
JBoss EAP 8.1 removes the following features.
name attribute removed from management model resources
In JBoss EAP 8.1, the name attribute has been removed from management model resources. The attribute has been deprecated since JBoss EAP 6.1 because it is redundant. The resource name is already part of the resource address.
This change can break existing CLI scripts that still use the name attribute. For example, a script that works in JBoss EAP 8.0 will fail in JBoss EAP 8.1 if the name attribute is present.
Example of a script that works in JBoss EAP 8.0
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file={path=server2.log,relative-to=jboss.server.log.dir},level=ALL,name=FILE2,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
{"outcome" => "success"}
Example of a script that fails in JBoss EAP 8.1
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file={path=server2.log,relative-to=jboss.server.log.dir},level=ALL,name=FILE2,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
'name' is not found among the supported properties: [append, autoflush, enabled, encoding, file, filter, filter-spec, formatter, level, named-formatter, suffix]
Corrected script without the name attribute (works in JBoss EAP 8.1)
[standalone@embedded /] /subsystem=logging/periodic-rotating-file-handler=FILE2:add(append=true,autoflush=true,enabled=true,file={path=server2.log,relative-to=jboss.server.log.dir},level=ALL,named-formatter=PATTERN,suffix=.yyyy-MM-dd)
{"outcome" => "success"}
4.3.1. --no-resolve-local-cache parameter Copy linkLink copied to clipboard!
The --no-resolve-local-cache parameter for the wildfly-jar-maven-plugin has been removed. The behavior previously enabled by this parameter is now default. The plugin no longer resolves artifacts from the local Maven cache by default.
To restore the previous default behavior of resolving artifacts from the local cache, you must now explicitly use the new --use-default-local-cache parameter in your configuration.