On (3) I'm not sure what this aspect factory is.
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.
To ease the life of the ContainerFactory I was also thinking that there
would be a ContainerMetaData abstraction.
This would be a specialization of the BeanMetaData targeted at the common
container configurations so...
1) The ContainerFactory doesn't has a simpler task
2) The ContainerFactory can spot the user has already preconfigured
some parts of container. In this case the container factory will just augment
the preconfigured container.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861651#3861651
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861651
-------------------------------------------------------
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
