Show Table of Contents
3.2.9. Service-style Deployment Changes
3.2.9.1. Update Applications That Use Service-style Deployments
Summary
MBeans were part of the core architecture in previous versions of Red Hat JBoss Enterprise Application Platform. JBoss Service Archive (SAR) deployments using the JBoss specific jboss-service.xml and jboss-beans.xml service-style descriptors were used by the application server to create MBeans based on JBoss Beans. The internal architecture has changed in JBoss EAP 6 and is no longer based on an MBean JMX architecture. MBeans are no longer part of the core architecture. They are now a wrapper for the management API.
If your application uses service-style deployment descriptors, it may continue to work in JBoss EAP 6 as long as it depends only on MBeans that your application defined and does not depend on the JBoss Management API MBean wrappers. In JBoss EAP 6, SARs can only declare MBean dependencies on MBeans that were created by another SAR deployment. This means if your application depended on MBeans that JBoss EAP created, such as an MBean for an EJB or messaging component, they will no longer work. The only MBeans you can depend on are other MBeans that you defined in other
jboss-service.xml files.
The JBoss Service Archive (SAR) and service-style descriptors used in previous versions of JBoss EAP are not a part of the Java EE 6 specification and are not recommended for use in JBoss EAP 6. It is recommended that you modify your application to the Java EE 6 specification. For MBeans singletons, you should modify the code to use the Java EE 6
@Singleton. For more information about creating and deploying MBean services, see the chapter entitled JBoss MBean Services in the Development Guide for JBoss Enterprise Application Platform 6 located on the Customer Portal at https://access.redhat.com/documentation/JBoss_Enterprise_Application_Platform/.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.