[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Adding applyMetaData method to KernelControllerContext
alesj
do-not-reply at jboss.com
Fri Aug 3 11:40:29 EDT 2007
"adrian at jboss.org" wrote : "alesj" wrote :
| | After you add new MetaData, it needs to be 'visited', in order to plugin all those dependencies, callbacks, installs, ...
| | So the easiest way for me to do that was to use the existing MetaDataVisitor concept, and just twist it a bit to suite my need - not starting from BeanMetaData, but on newly added MetaDataVisitorNode + pushing BMD at the bottom of the stack before executing it.
| |
| Ok. But I'm not sure it needs to be this complicated?
|
Complicated?
This is what looked natural to me, to use existing visitor concept.
Since we are already in Describe state, executing both of them - initial and describe. No need for changing existing MetaData impl.
What would you do?
"adrian at jboss.org" wrote :
| anonymous wrote :
| | When we do a re-install on the controller context, do we need a new look at the annotations?
| |
|
| Of course, the class could change.
|
Yup.
Can you give a scenario how this would work and that the underlying controller context wouldn't be removed during that process?
Probably if we remove the underlying Classloader, context gets unistalled - into PreInstall state - and then re-installed with new Classloader. Will that do? :-)
"adrian at jboss.org" wrote :
| Ok. So the code that didn't compile was just out-of-the-box factory settings
| for bootstrapping?
The JavaBeanAnnotationPlugin?
I think the compiling problem was simply because I had some classes locally which my IDEA/SVN didn't 'noticed', so they weren't commited.
Or which problem do you have in mind?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070686#4070686
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070686
More information about the jboss-dev-forums
mailing list