[jboss-dev] jbossas -beans.xml opt

[Jason T. Greene]

Ok, so then, why do we need AOPDependencyBuilder to use @JMX? Yes I know 
the dep builder allows for users to add aspects after the fact, but this 
is a near *useless* feature, especially for our core components.

Brian Stansberry wrote:
> The registration of the @JMX handling is in the bootstrap, in 
> bootstrap/jmx.xml.
> 
> Jason T. Greene wrote:
>> Ales Justin wrote:
>>> (2) @org.jboss.aop.microcontainer.annotations.DisableAOP
>>>
>>> This one instructs MC to ignore transparent AOP usage when handling 
>>> your bean.
>>> It will not look for aspect dependencies or try to create an AOP proxy.
>>> It will simply fall back to plain POJO handling.
>>>
>>> If you use @JMX or anything similar, this should then *not* be used.
>>> But for anything else it should be good to use it.
>>
>> Can we fix the @JMX (and other known cases) by deploying them sooner, 
>> as part of the bootstrap for example?
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
>