"[EMAIL PROTECTED]" wrote : On (3) I'm not sure what this aspect factory is.
Well, integrated with the MC the aspect factory would be responsible for
registering its dependencies to the MC. IT would also be responsible for
allocating instances of aspects based on their scope. (PER_VM, PER_CLASS,
etc...)
anonymous wrote :
| I do agree that some metadata/config will only be known when we resolve the
| annotations from the class. Whether this is done by the aspect factory I
don't know.
|
| From the MC view point I was thinking of an integration point like:
|
|
| | public ContainerFactory
| | {
| | BeanMetaData createContainer(BeanMetaData bmd)
| | }
| |
| that gets invoked at "describe" time in the lifecycle.
|
| This says take the requested BeanMetaData and replace it with a bean
| wrapped in a container + all its resolved metadata.
|
Will BeanMetaData have an API to register dependencies? SO that the container
or container factory can decide what dependencies it requires and so you can
support all that stuff I talked about before where the aspect knows its
dependencies, not the bean?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861655#3861655
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861655
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
