JSR-77 Implementation

[haneef]

Hi,

MEJB interface defined in JBOSS seems to have more methods than one defined in JSR-77 (atleast 5 more methods). Is JBOSS really JSR-77 compliant or any plans of making it JSR-77 Compliance

Thanks,
Haneef

[juha]

It may be that the interfaces changed a bit between when the implementation of 77 was written and the spec went final.

However, I don't know if anyone is maintaining the 77 implementation at the moment.

[mclaugs]

I am maintaining (when I have time) the JSR 77 implementation. Looking at the MEJB I only see two methods that are not defined in the jsr. createMBean and unregisterMBean. The JSR states that a compliant implementation must expose the interface defined in Section JSR77.7.3.2, The spec says nothing about extending it, other then it is allowed as long as the defined interface is implemented as specified.

As far as does JBoss intend to become JSR 77 compliant
the answer is yes, when I have time. If you are interested in helping out let me know and I can help you in getting started.

Also if you would, what 5 methods are you referring to?

[perfman123]

Does this mean that currently none of the (runtime)statistics defined in JSR77 are implemented? I would appreciate any information on the current status of this effort and might be interested in contributing.

[juha]

statistics not implemented at the moment, as far as I know

[paci]

Hi,

We plan to incorporate lots of JMX on all platforms supported (WAS, WLS, JBoss), but the implementations vary so much that it's not easy. That's why we cannot support all platforms! All platforms seem to have their own twists, and this means we have to detect the server and install appropriate components.

I'm trying integrate certain things to our framework and right now I'm desperately seeking for a way to get notification when the application goes down. I'm not interested in EJB or Web modules, just when the whole application is stopped. (I have to tidy up dynamically registered MBeans for example). I have already implemented this for WebSphere 5.0 and WebLogic 8.1, but JBoss seems to be a troublemaker for my implementation. The way I have implemented it in other platforms is that I'm registering my own listener for application and waiting for j2ee.state.stopping (in WebSphere) or something WebLogic specific. However, JBoss application doesn't seem to broadcast any notifications (unlike WebSphere and WebLogic Server), and I kind of understand it since the object is not state manageable in JBoss. But it would be really nice if it was! Any plans to make it state manageable? I can probably do this by some other means too, but I would like to follow the standard (or at least close to it) as much as possible. (In fact there's no mention in the spec which objects should be state manageable, which I see rather confusing and irrational). Anybody else struggling with this issue?

Thanks in advance,

Pasi Salminen
CTO
ProfitSoftware Ltd

[paci]

Hi,

We plan to incorporate lots of JMX on all platforms supported (WAS, WLS, JBoss), but the implementations vary so much that it's not easy. That's why we cannot support all platforms! All platforms seem to have their own twists, and this means we have to detect the server and install appropriate components.

I'm trying integrate certain things to our framework and right now I'm desperately seeking for a way to get notification when the application goes down. I'm not interested in EJB or Web modules, just when the whole application is stopped. (I have to tidy up dynamically registered MBeans for example). I have already implemented this for WebSphere 5.0 and WebLogic 8.1, but JBoss seems to be a troublemaker for my implementation. The way I have implemented it in other platforms is that I'm registering my own listener for application and waiting for j2ee.state.stopping (in WebSphere) or something WebLogic specific. However, JBoss application doesn't seem to broadcast any notifications (unlike WebSphere and WebLogic Server), and I kind of understand it since the object is not state manageable in JBoss. But it would be really nice if it was! Any plans to make it state manageable? I can probably do this by some other means too, but I would like to follow the standard (or at least close to it) as much as possible. (In fact there's no mention in the spec which objects should be state manageable, which I see rather confusing and irrational). Anybody else struggling with this issue?

Thanks in advance,

Pasi Salminen
CTO
ProfitSoftware Ltd