org.springframework.jmx.support Documentation Differences

This file contains all the changes in documentation in the package org.springframework.jmx.support as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Provides supporting infrastructure for registering MBeans with an javax.management.MBeanServer. The behavior when encountering an existing MBean at a given ObjectName is fully configurable allowing for flexible registration settings.

All registered MBeans are tracked and can be unregistered by calling the #.unregisterBeans() method.

Sub-classes can receive notifications when an MBean is registered or unregistered by overriding the .onRegister(ObjectName) and .onUnregister(ObjectName) methods respectively.

By default, the registration process will fail if attempting to register an MBean using a javax.management.ObjectName that is already used.

By setting the registrationBehaviorNameregistrationPolicy property to REGISTRATION_RegistrationPolicy.IGNORE_EXISTING the registration process will simply ignore existing MBeans leaving them registered. This is useful in settings where multiple applications want to share a common MBean in a shared MBeanServer.

Setting registrationBehaviorNameregistrationPolicy property to REGISTRATION_RegistrationPolicy.REPLACE_EXISTING will cause existing MBeans to be replaced during registration if necessary. This is useful in situations where you can't guarantee the state of your MBeanServer. @author Rob Harrop @author Juergen Hoeller @author Phillip Webb @since 2.0 @see #setServer @see #setRegistrationBehaviorName setRegistrationPolicy @see org.springframework.jmx.export.MBeanExporter

Specify what action should be taken when attempting to register an MBean under an javax.management.ObjectName that already exists.

Default is REGISTRATION_FAIL_ON_EXISTING. @see #setRegistrationBehaviorName(String) @see #REGISTRATION_FAIL_ON_EXISTING @see #REGISTRATION_IGNORE_EXISTING @see #REGISTRATION_REPLACE_EXISTINGEXISTING @deprecated since Spring 3.2, in favor of .setRegistrationPolicy(RegistrationPolicy)

Set the registration behavior by the name of the corresponding constant, e.g. "REGISTRATION_IGNORE_EXISTING". @see #setRegistrationBehavior @see #REGISTRATION_FAIL_ON_EXISTING @see #REGISTRATION_IGNORE_EXISTING @see #REGISTRATION_REPLACE_EXISTINGEXISTING @deprecated since Spring 3.2, in favor of .setRegistrationPolicy(RegistrationPolicy)

Constant indicating that registration should fail when attempting to register an MBean under a name that already exists.

This is the default registration behavior. @deprecated since Spring 3.2, in favor of RegistrationPolicy.FAIL_ON_EXISTING

Constant indicating that registration should ignore the affected MBean when attempting to register an MBean under a name that already exists. @deprecated since Spring 3.2, in favor of RegistrationPolicy.IGNORE_EXISTING

Constant indicating that registration should replace the affected MBean when attempting to register an MBean under a name that already exists. @deprecated since Spring 3.2, in favor of RegistrationPolicy.REPLACE_EXISTING

FactoryBean that obtains a WebSphere javax.management.MBeanServer reference through WebSphere's proprietary AdminServiceFactory API, available on WebSphere 5.1 and higher.

Exposes the MBeanServer for bean references. This FactoryBean is a direct alternative to MBeanServerFactoryBean, which uses standard JMX 1.2 API to access the platform's MBeanServer.

See Javadoc for WebSphere's {@code AdminServiceFactory} and {@code MBeanFactory}. @author Juergen Hoeller @author Rob Harrop @since 2.0.3 @see com.ibm.websphere.management.AdminServiceFactory#getMBeanFactory() @see com.ibm.websphere.management.MBeanFactory#getMBeanServer() @see javax.management.MBeanServer @see MBeanServerFactoryBean