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

[jaikiran]

In the meantime,

"alesj" wrote : "jaikiran" wrote : 
  |   | 1) Can the AOPDependencyBuilder be removed as the default 
  |   | 
  | No, as this would break all the @JMX definitions.
  | Plus probably a ton of other stuff. ;-)
  | 
I agree, there's going to be some stuff which going to be break (till we fix it :) ). But in the long term, shouldn't we be moving away from this default? Here's why i think the AOPDependencyBuilder default might not be a good idea:

1) For non-programmatic MC bean deployments (i.e. just drop the -beans.xml file), there's no way to override this default dependency builder

2) Even for programmatic MC bean deployments, not everyone will be aware of this issue (or the internal implementation of MC), so most of the times, they are going to end up without any overridden (better performing) dependency builder in the metadata

3) If this dependency builder is for beans that use @JMX or something similar, then i guess there might be some place where this AOPDependencyBuilder can be attached/injected internally by MC to ensure that only such deployments are handled by this builder?




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

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