"adrian(a)jboss.org" wrote :
| The best you can do (in general) is remember that a
| contextual injection was done and if another candidate
| appears after the fact then issue a warning.
|
Where to hold such information?
anonymous wrote : assuming you are talking about annotations
That too (see below).
But what about actual @Inject in class annotation?
Where to look/inspect class for them - to add dependency 'demand' items - how to
get bean class from AbstractDependencyValueMetaData?
anonymous wrote :
| AbstractKernelController.preprocessMetaData()
| is where this gets done (assuming you are talking about annotations).
| However when we do classloading dependencies, some of this
| will have to move to the DescribeAction such that we know
| the class exists.
How to add specific code about @Inject annotation into AnnotationMetaData.visit() -
through children?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964979#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...