JDK-6577604 : MBeanServerNotificationFilter should support ObjectName wildcards
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2007-07-06
  • Updated: 2010-07-29
  • Resolved: 2008-06-18
Related Reports
Relates :  
JDK-6610917 - Define a generic NotificationFilter
Description
The class javax.management.relation.MBeanServerNotificationFilter allows you to receive registration and/or unregistration notifications for a subset of MBean names.  It is configured by adding the names to a list.  The meaning of adding an ObjectName pattern is obvious but in fact it does not work.  The MBeanServerNotificationFilter class allows the pattern to be added, but since it only compares names for equality the pattern has no effect.

The class should be changed so that patterns work.
Comments
EVALUATION The new QueryNotificationFilter class provides this functionality, with a more obvious failure mode when a recent client tries to use it against a server that doesn't have the functionality. Ideally we would change MBeanServerNotificationFilter so that it explicitly rejects wildcards, but there is some danger of breaking existing code that does so (presumably unintentionally). Therefore we are not planning to fix this.
18-06-2008
WORK AROUND Define your own NotificationFilter class with the desired semantics. But then client and server will both have to be configured to have this class present.
06-07-2007
EVALUATION Should be simple. We can make this change in Java SE 7.
06-07-2007