java.lang.Objectjavax.management.NotificationFilterSupport
All Implemented Interfaces:
NotificationFilter
Direct Known Subclasses:
MBeanServerNotificationFilter
Manages a list of enabled notification types. A method allows users to enable/disable as many notification types as required.
Then, before sending a notification to a listener registered with a filter, the notification broadcaster compares this notification type with all notification types enabled by the filter. The notification will be sent to the listener only if its filter enables this notification type.
Example:
The listenerNotificationFilterSupport myFilter = new NotificationFilterSupport(); myFilter.enableType("my_example.my_type"); myBroadcaster.addListener(myListener, myFilter, null);
myListener
will only receive notifications the type of which equals/starts with "my_example.my_type".1.5
- Method from javax.management.NotificationFilterSupport Summary: |
---|
disableAllTypes, disableType, enableType, getEnabledTypes, isNotificationEnabled |
Methods from java.lang.Object: |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Method from javax.management.NotificationFilterSupport Detail: |
---|
|
If the specified prefix is not in the list of enabled notification types, this method has no effect. |
If the specified prefix is already in the list of enabled notification types, this method has no effect. Example: Note that:// Enables all notifications the type of which starts with "my_example" to be sent. myFilter.enableType("my_example"); // Enables all notifications the type of which is "my_example.my_type" to be sent. myFilter.enableType("my_example.my_type");
will no match any notification type. |
|
This filter compares the type of the specified notification with each enabled type. If the notification type matches one of the enabled types, the notification should be sent to the listener and this method returns true . |