[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: DESCRIBE phase - Dependency builders for MC Beans

[jaikiran]

"alesj" wrote : "jaikiran" wrote : But in the long term, shouldn't we be moving away from this default?
  |   | 
  | No, that's why it's called *transparent* AOP integration. ;-)
  | 
  | You can only argue that the AOP mechanism is not performant enough,
  | but that's as far as I agree with you.
  | Although this comes with a cost, it does bring lots of nice features.
  | They are mostly true in a sense of AOP; aspects, concerns separation, ...
  | @JMX, @JNDI, @Password, @(add-your-own-metadata-here) are good examples of this.
  | And if I was a user, that's what I would want too, out-of-the-box.
  | 
I am not against using AOP, where its needed :) In the current scenario, there was no way to tell MC that i did not want AOP 

"alesj" wrote : 
  | But yeah, there should be a way to explicitly avoid this,
  | and this is/can be achieved with this new DB per MD mechanism.
  | And if there is a real demand for this "outside" programmatic usage,
  | it's trivial to add new declarative way of using this.

"kabir.khan at jboss.com" wrote : An annotation could be used on the deployment or per bean, e.g. @NoAop
Yes, this now allows us a way to skip/override the defaults.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230384#4230384

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230384