Chapter 8. Miscellaneous changes This section provides an overview of the various miscellaneous changes happening in this release. 8.1. Changes to delivery of JBoss EAP Natives and Apache HTTP Server JBoss EAP 8.0 natives are delivered differently in this release than in JBoss EAP 6. Some components include Red Hat JBoss Core Services product, which is a set of supplementary software that is common to many of the Red Hat JBoss middleware products. The new product allows for faster distribution of updates and a more consistent update experience. The JBoss Core Services product is available for download in a dedicated location on the Red Hat Customer Portal. The following table lists the differences in the delivery methods between the releases. Package JBoss EAP 6 JBoss EAP 8.0 AIO Natives for Messaging Delivered with the product in a separate "Native Utilities" download Included within the JBoss EAP distribution. Apache HTTP Server Delivered with the product in a separate "Apache HTTP Server" download Delivered with the new JBoss Core Services product mod_cluster, mod_jk, isapi, and nsapi connectors Delivered with the product in a separate "Webserver Connector Natives" download Delivered with the new JBoss Core Services product JSVC Delivered with the product in a separate "Native Utilities" download Delivered with the new JBoss Core Services product OpenSSL Delivered with the product in a separate "Native Utilities" download Delivered with the new JBoss Core Services product tcnatives Delivered with the product in a separate "Native Components" download Support for tcnatives was removed in JBoss EAP 7 Additional changes for JBoss EAP Natives and Apache HTTP Server You should also be aware of the following changes: Support was dropped for mod_cluster and mod_jk connectors used with Apache HTTP Server from Red Hat Enterprise Linux RPM channels. If you run Apache HTTP Server from Red Hat Enterprise Linux RPM channels and need to configure load balancing for JBoss EAP 8.0 servers, you can do one of the following: Use the Apache HTTP Server provided by JBoss Core Services. You can configure JBoss EAP 8.0 to act as a front-end load balancer. For more information, see Configuring JBoss EAP as a Front-end Load Balancer in the JBoss EAP 7.4 Configuration Guide . You can deploy Apache HTTP Server on a machine that is supported and certified and then run the load balancer on that machine. For the list of supported configurations, see Overview of HTTP Connectors in the JBoss EAP 7.4 Configuration Guide . You can find more information about JBoss Core Services in the Apache HTTP Server Installation Guide . You can configure JBoss EAP 8.0 to act as a front-end load balancer. For more information, see Configuring JBoss EAP as a Front-end Load Balancer in the JBoss EAP Configuration Guide . You can deploy Apache HTTP Server on a machine that is supported and certified and then run the load balancer on that machine. For the list of supported configurations. You can find more information about JBoss Core Services in the Apache HTTP Server Installation Guide . 8.2. Changes to deployments on Amazon EC2 Several changes have been made to the Amazon Machine Images (AMI) in JBoss EAP 7. This section briefly summarizes some of those changes. The way you start non-clustered and clustered JBoss EAP instances and domains in Amazon EC2 has changed significantly. In JBoss EAP 6, configuration depended on the User Data: field. In JBoss EAP 7, the AMI scripts that parsed the configuration in the User Data: field and started the servers automatically on instance startup have been removed. Red Hat JBoss Operations Network agent was installed in the JBoss EAP 6. Starting with JBoss EAP 7.0, you must install it separately. For details on deploying JBoss EAP 7 on Amazon EC2, see Deploying JBoss EAP on Amazon Web Services . 8.3. Remove applications that include shared modules Changes introduced in the JBoss EAP 7.1 server and the Maven plug-in can result in the following failure when you attempt to remove your application. This error can occur if your application contains modules that interact with or depend on each other. For example, assume you have an application that contains two Maven WAR project modules, application-A and application-B , that share data managed by the data-sharing module. When you deploy this application, you must deploy the shared data-sharing module first, and then deploy the modules that depend on it. The deployment order is specified in the <modules> element of the parent pom.xml file. This is true in JBoss EAP 6.4 through JBoss EAP 8.0. In releases prior to JBoss EAP 7.1, you could undeploy all of the archives for this application from the root of the parent project using the following command. In JBoss EAP 7.1 and later, you must first undeploy the archives that use the shared modules, and then undeploy the shared modules. Since there is no way to specify the order of undeployment in the project pom.xml file, you must undeploy the modules manually. You can accomplish this by running the following commands from the root of the parent directory. This updated undeploy behavior is more accurate and ensures that you do not end up in an unstable deployment state. 8.4. Changes to the add-user script The add-user script behavior has changed in JBoss EAP 7 due to a change in password policy. JBoss EAP 6 had a strict password policy. As a result, the add-user script rejected weak passwords that did not satisfy the minimum requirements. Starting with JBoss EAP 7, weak passwords are accepted and a warning is issued. For more information, see Setting Add-User Utility Password Restrictions in the JBoss EAP 7.4 Configuration Guide . 8.5. Removal of OSGi support When JBoss EAP 6.0 GA was first released, JBoss OSGi, an implementation of the OSGi specification, was included as a Technology Preview feature. With the release of JBoss EAP 6.1.0, JBoss OSGi was demoted from Technology Preview to Unsupported. In JBoss EAP 6.1.0, the configadmin and osgi extension modules and subsystem configuration for a standalone server were moved to a separate EAP_HOME /standalone/configuration/standalone-osgi.xml configuration file. Because you should not migrate this unsupported configuration file, the removal of JBoss OSGi support should not impact the migration of a standalone server configuration. If you modified any of the other standalone configuration files to configure osgi or configadmin , those configurations must be removed. For a managed domain, the osgi extension and subsystem configuration were removed from the EAP_HOME /domain/configuration/domain.xml file in the JBoss EAP 6.1.0 release. However, the configadmin module extension and subsystem configuration remain in the EAP_HOME /domain/configuration/domain.xml file. Starting with JBoss EAP 7, this configuration is no longer supported and must be removed. 8.6. Changes in SOAP with Attachments API for Java Update the user-defined SOAP handlers to comply with the SAAJ 3.0 specification when migrating to JBoss EAP 8.0. Additional resources Jakarta Soap with Attachments

Commands:
WFLYCTL0184: New missing/unsatisfied dependencies
mvn wildfly:undeploy
mvn wildfly:undeploy -pl application-A,application-B mvn wildfly:undeploy -pl data-shared