[jboss-dev] jbossas -beans.xml opt

[Ales Justin]

Sure, I never implied it is the same.
I might wrote it in a confusing way.

AOP is there from day one --> @DisableAOP

@IoC & jsr-299 --> our MC IoC should support that too; annotation  
based ioc

And we don't use AOP with our MC @IoC.
Just MDR, for already stated reasons.

Sent from my iPhone

On May 14, 2009, at 19:15, "Jason T. Greene" <jason.greene at redhat.com>  
wrote:

> Ales Justin wrote:
>> There is no magic.
>> We know AOP is there from day one,
>> and @annotation based IoC handling is a-must-have in these jsr-299  
>> days.
>>
>> It's just that the sole nature of these mechanisms is not very  
>> performance friendly.
>
> Annotation IoC handling != AOP. This is just an implementation we  
> chose. The JSR-299 RI for example does not require AOP.
>
> The AOP dependency processing "magic" is a great example of  
> something we don't need for container provided annotations like  
> @JMX. Those should all be registered up-front.
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development