Re: javax.management woes, again

2007-05-08 Thread Andrew Haley
Andrew John Hughes writes: > On Wednesday 02 May 2007 17:15, Andrew Haley wrote: > > This is an FYI regarding javax.management in Fedora 7. Comments from > > Classpath hackers welcome... > > Thanks for fixing this. I don't see a mention of the notification in the > online API which is, I

Re: javax.management woes, again

2007-05-07 Thread Andrew John Hughes
On Wednesday 02 May 2007 17:15, Andrew Haley wrote: > This is an FYI regarding javax.management in Fedora 7. Comments from > Classpath hackers welcome... > > Andrew. Thanks for fixing this. I don't see a mention of the notification in the online API which is, I guess, why I missed it. Thanks a

Re: javax.management woes, again

2007-05-03 Thread Andrew Haley
Hmm. Looks like we need to start counting sequence numbers at 1 because MBeanServerDelegate.sendNotification sends delegate's own sequence number if the supplied notification has a sequence number is <= 0. Andrew. 2007-05-03 Andrew Haley <[EMAIL PROTECTED]> * gnu/javax/management/Se

Re: javax.management woes, again

2007-05-03 Thread Andrew Haley
Fixes https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236541. Andrew. 2007-05-03 Andrew Haley <[EMAIL PROTECTED]> * gnu/javax/management/Server.java (Server): Record the delegate. (registerMBean): Notify the delegate. (unregisterMBean): Likewise. (notify):

javax.management woes, again

2007-05-02 Thread Andrew Haley
This is an FYI regarding javax.management in Fedora 7. Comments from Classpath hackers welcome... Andrew. --- Begin Message --- To cut to the chase: I've been debugging 236541 for a week now, and I've finally found the cause: gnu.javax.management.Server.registerMBean() is broken in Classpath.