Hi
Sorry for your trouble because I am the one who made the conversion from the
beta JMX to the final release (1.0).
Yeah, I forgot that the other modules can be affected and only tested it for
jBoss
BUT I wrote more than one mails in jBoss-Dev about this.
I don't think there is an easy way to handle this. Maybe we can have an HTML
document about the important changes on their way or already done because
if you are out for vacation or due to your job then you can easily miss such
information.
Have fun - Mad Andy
----- Original Message -----
From: "Vincent Sheffer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 26, 2000 3:09 PM
Subject: [jBoss-Dev] JMX Changes in jBOSS Broke SpyderMQ Integration
> There were some changes to the jmxri.jar file used by jBoss on Sep.
> 8. After that change the jmxri.jar file used by jBoss differed from
> that used by SpyderMQ, thus breaking the integration with jBoss and
> SpyderMQ. Finding the problem proved to be very difficult (once I
> realized the change had been made it was very easy to fix, but realizing
> this was not easy). When someone makes a change to jBoss that might
> affect some of the other modules under jBoss, who's responsible for
> making the change to the other modules? Even though we get notified of
> changes made in CVS via the developers mailing list it is easy for these
> changes to go unnoticed, as happened in this case.
>
> vince
>
> --
> ________________________________
> Vincent Sheffer
> Director of Operations
> Telkel, Inc.
> ________________________________
>
>
