On 01/03/2010 09:05 AM, Bill Burke wrote:
> True, but we use @JMX all over the place. I expect trying to get
> it and having all our POJO services register themselves in JMX will end
> up sucking in most of the AS team, which will be a significant
> distraction from EE 6 work. Personally I think we should explore further
> whether this can be optimized before going down that path.
This is something I wouldn't mind doing if Kabir finds that AOP can't be
The fact that @JMX uses AOP is an implementation detail. Surely there's a
non-AOP way to do this, which doesn't involve every service registering
itself in JMX?