[Jboss-dev-forums] [Design the new POJO MicroContainer] - Re: AOP/Metadata integration config

[<ad...@jb...>]

"bil...@jb..." wrote : I don't think you understand how I am doing this AOP/MC integration.
  | 

It is more likely I don't understand your own description of what you have done :-)

anonymous wrote : anonymous wrote : 
  |   | In the MC if the advice and its dependencies are not installed the object is not created
  |   | and the user is told to deploy the missing dependency.
  |   | 
  | 
  | And this works, so what is the problem?  ClassAdapter.getDependencies() is currently called before class static initialization and the aspect dependencies propagated.  Did you see that I implemented and tested this?
  | 

Yes.

anonymous wrote : 
  | The SecurityDomain example is a different example.  This is because knowledge of the dependency is hidden in the annotations.  
  | 

I thought you had started arguing that this could not be done?

anonymous wrote : 
  | So, I thought our agreement was that this annotation would have a @Dependency annotation on it:
  | 

Yes.

anonymous wrote : 
  | Either the MC or AOP is gonna have to look at every single annotation attached to the class (and superclass) for this @Dependency annotation and add it to the BeanMetaData dependency list.  Correct?  I'm fine with adding this to the AspectAdapter.
  | 

I don't think it matters who does it as long as it gets done. I thought we agreed
that it would be done by MC since it could be potentially looking at classes
that AOP doesn't care about.

The main issue now I think is how the MC gets hold of the annotations if there
is no ClassInfo. It looks like it falling back on reflection.

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

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