Automatic Registration Of @Singleton EJBs As MXBeans about ejb-spec HOT 10 CLOSED

Reported by abien

from ejb-spec.

jlmonteiro said:
As already discussed, that'd be great.
Just not sure if we have to create a new annotation or if we can ask JSR 255 spec lead or members, if they can release.

Thoughts?

Jean-Louis

from ejb-spec.

benoitf said:
Except that we couldn't have attributes for SLSB, it could be interesting to expose the SLSB method as JMX operations

from ejb-spec.

mvatkina said:
(Unfortunately) I'm closing this issue for the following reasons:

• JMX usage is declining with the REST APIs being used instead. If the REST related improvements or integration points need to be addressed, let's start a separate discussion.

• Even if there is still enough interest in the JMX improvements, any changes to the JMX support should be done across the platform, rather than in a piecemeal fashion in a subset of technologies (even worse, only in one), i.e. it would be at minimum very confusing to the users, if the EJB container provides some special JMX handling that is not available in any other technology. Anybody interested in driving the effort of adding new features to the JMX or the JMX/EE integration would need to start a new JSR for a revision of the JMX spec.

from ejb-spec.

rherschke said:
Maybe we can have at least a @resource injection of the platformmbeanserver instead?
So one can implement an interceptor with @AroundConstruct to do the registration.

This would pass the rule of separating concerns and will get a clear EJB Pojo as well.

Example:

@Inherited
@InterceptorBinding
@Target({TYPE}) @Retention(RUNTIME) public @interface MBean {
    @NotBinding String value() default "";
}

@Interceptor @MBean
public class MBeanInterceptor {

    @Resource
    MBeanServer server;

    @PostConstruct
    public void registerBean(InvocationContext ctx) {
        ctx.proceed();
        ObjectName on = ... // get objectname from annotation value
        server.register(on, ctx.getTarget());
        // or do the neccessary DynamicMBean work here...
    }

    @PreDestroy
    public void unregister(InvocationContext ctx) {
        ObjectName on = ... // get objectname from annotation
        server.unregister(on);
        ctx.proceed();
    }
}

@Singleton @Startup @MBean("com.example:type=MyMXBean")
public class MyMXBean {
// ... }

So with @resource injection, this will work even on appservers with its own MBeanServer, not only with JVM PlatformServer, but the developer do not care about this.

Next, @resource injection could be used also in a normal EJB to do some client work (observe notifications, get attributes aso.) with a registered mbean without the need to distinguish about the right MBeanServer to be used.

from ejb-spec.

mvatkina said:
This functionality, if available, should not be limited to the EJBs ("any changes to the JMX support should be done across the platform"), correct? If so, I suggest to open the request in the javaee-spec project.

from ejb-spec.

rherschke said:
@marina, you're right.

see: http://java.net/jira/browse/JAVAEE_SPEC-21

from ejb-spec.

Was assigned to mvatkina

from ejb-spec.

This issue was imported from java.net JIRA EJB_SPEC-32

from ejb-spec.

Marked as won't fix on Tuesday, July 10th 2012, 6:04:28 pm

from ejb-spec.