Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Incomplete
-
Affects Version/s: 1.0-beta-1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The NanoMX code decorates the bean with a Dynamic MBean, which hides needed interface info from the JMX server.
For example, when I tried to add a notification to a managed javax.management.Timer bean (which was wrapped by a NanoMBean) the server told me that the bean didn't implement NotificationBroadcaster even though it does.
My solution was to remove the decorator instance and go with the
assumption that the component has an *MBean interface so that it can be recognized as a "Standard MBean".
I don't think this is a very big requirement to make of the components
for this container since Pico recommends interfaces anyways. However if
you have a simple way of dynamically making the decorator look like it
implements everything that the delegate implements, then that would be
the best way to go.
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Aslak Hellesoy [ rinkrank ] | |
Status | Unassigned [ 1 ] | Assigned [ 2 ] |
Resolution | Incomplete [ 4 ] | |
Status | Assigned [ 2 ] | Closed [ 6 ] |
Do you have a patch? I'm not quite sure what exactly you're asking for.