Fix deprecated property in MBeanExporter documentation

Closes gh-1991
This commit is contained in:
Christian Kulpa 2018-10-12 16:02:27 +02:00 committed by Stephane Nicoll
parent bfc5ad890e
commit 864d7eaf11
1 changed files with 8 additions and 9 deletions

View File

@ -3440,33 +3440,32 @@ The following table summarizes these registration behaviors:
|=== |===
| Registration behavior | Explanation | Registration behavior | Explanation
| `REGISTRATION_FAIL_ON_EXISTING` | `FAIL_ON_EXISTING`
| This is the default registration behavior. If an `MBean` instance has already been | This is the default registration behavior. If an `MBean` instance has already been
registered under the same `ObjectName`, the `MBean` that is being registered is not registered under the same `ObjectName`, the `MBean` that is being registered is not
registered, and an `InstanceAlreadyExistsException` is thrown. The existing registered, and an `InstanceAlreadyExistsException` is thrown. The existing
`MBean` is unaffected. `MBean` is unaffected.
| `REGISTRATION_IGNORE_EXISTING` | `IGNORE_EXISTING`
| If an `MBean` instance has already been registered under the same `ObjectName`, the | If an `MBean` instance has already been registered under the same `ObjectName`, the
`MBean` that is being registered is not registered. The existing `MBean` is `MBean` that is being registered is not registered. The existing `MBean` is
unaffected, and no `Exception` is thrown. This is useful in settings where unaffected, and no `Exception` is thrown. This is useful in settings where
multiple applications want to share a common `MBean` in a shared `MBeanServer`. multiple applications want to share a common `MBean` in a shared `MBeanServer`.
| `REGISTRATION_REPLACE_EXISTING` | `REPLACE_EXISTING`
| If an `MBean` instance has already been registered under the same `ObjectName`, the | If an `MBean` instance has already been registered under the same `ObjectName`, the
existing `MBean` that was previously registered is unregistered, and the new existing `MBean` that was previously registered is unregistered, and the new
`MBean` is registered in its place (the new `MBean` effectively replaces the `MBean` is registered in its place (the new `MBean` effectively replaces the
previous instance). previous instance).
|=== |===
The values in the preceding table are defined as constants on the `MBeanRegistrationSupport` class (the The values in the preceding table are defined as enums on the `RegistrationPolicy` class.
`MBeanExporter` class derives from this superclass). If you want to change the default If you want to change the default registration behavior, you need to set the value of the
registration behavior, you need to set the value of the `registrationPolicy` property on your `MBeanExporter` definition to one of those
`registrationBehaviorName` property on your `MBeanExporter` definition to one of those
values. values.
The following example shows how to change from the default registration The following example shows how to change from the default registration
behavior to the `REGISTRATION_REPLACE_EXISTING` behavior: behavior to the `REPLACE_EXISTING` behavior:
==== ====
[source,xml,indent=0] [source,xml,indent=0]
@ -3480,7 +3479,7 @@ behavior to the `REGISTRATION_REPLACE_EXISTING` behavior:
<entry key="bean:name=testBean1" value-ref="testBean"/> <entry key="bean:name=testBean1" value-ref="testBean"/>
</map> </map>
</property> </property>
<property name="registrationBehaviorName" value="REGISTRATION_REPLACE_EXISTING"/> <property name="registrationPolicy" value="REPLACE_EXISTING"/>
</bean> </bean>
<bean id="testBean" class="org.springframework.jmx.JmxTestBean"> <bean id="testBean" class="org.springframework.jmx.JmxTestBean">