Re: [jboss-dev] @JMX and @DisableAOP live happily together
As far as I'm aware, MBeans don't normally have lifecycle methods outside
of the methods on f.e. MBeanRegistration or PersistentMBean or whatever (in
other words, managed by the MBeanServer and not the MC). If the bean's
mbean view is being registered to the MBeanServer, what else could it be
doing that it's not?
The idea that @JMX doesn't work with @DisableAOP was (iirc) the primary
argument against having AOP disabled by default, but it seems to me that
this is not true.
- DML
On 05/18/2009 10:51 AM, Kabir Khan wrote:
Looks like a user error ;-) Or are you saying it actually invokes the
lifecycle callback in this case?
On 18 May 2009, at 17:40, David M. Lloyd wrote:
> So why should @DisableAOP be the annotation with enabling AOP being
> the default?
>
> <?xml version="1.0" encoding="UTF-8"?>
>
> <deployment xmlns="urn:jboss:bean-deployer:2.0">
> <bean name="TestBean"
class="javax.management.monitor.GaugeMonitor">
>
<annotation>(a)org.jboss.aop.microcontainer.annotations.DisableAOP()</annotation>
>
>
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(exposedInterface=javax.management.monitor.GaugeMonitorMBean,name="test:name=Banana",registerDirectly=false)</annotation>
>
> </bean>
> </deployment>
>
> - DML
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development