"ALRubinger" wrote : | We've currently got @Service, which deploys a Singleton EJB and exposes a JMX View. Oftentimes this is used strictly to get a hook into a Lifecycle (ie. "I want a callback for when my JAR is deployed"). And JMX exposure is not necessarily desired. | @Service ~ MC's @JMX MC beans are 'singletons' in MC (not prototypes). And you can of course code it via factory instantiation to be 'real' singletons (one per CL ... dunno how you achieve that for VM though). "ALRubinger" wrote : | I'd like to introduce the notion of an MC EJB, which would have the following features: | | 1) Full EJB (Tx, Security, etc) | 2) @Singleton (Same model following EJB3.1 with regards to concurrency) | 3) POJO w/ annotations to denote Callbacks (@Service requires Management interface) | 4) Proxy is installed into MC and therefore becomes a valid MC Bean; though when MC POJOs invoke on the EJB MC Bean, a typical EJB call starts. | 1) If you have matching aspects for it (@Tx --> Tx aspect, ...) this comes out-of-the-box in MC ... the bean will be aspectized - a JBossAop proxy. Or you can install it into MC with already created instance, as we've discussed it before. 2) As explained above 3) Annotation handling is pluggable; e.g. ejb's @Create can be mapped to MC's create notion ... see how we handle MC's @Create 4) Sure, once it's in MC anyone can invoke it ... if the injection happens by name, then you might consider On_Demand mode. Or perhaps my Lazy hack - we can discuss this further, if previous solutions don't work for you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153874#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...