"jaikiran" wrote :
| That's the whole point, this is a dynamic MC bean created on the fly with
no xml configuration :)
OK, I still don't consider this a valid use case to make MC changes. :-)
But keeps us informed on how you achieved this. ;-)
View the original post :
http://www.jboss.org/ind
"alesj" wrote :
|
| .. as well in MC's xml descriptor. ;-)
That's the whole point, this is a dynamic MC bean created on the fly with no
xml configuration :)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212865#4212865
Reply to the post :
http://www.j
"jaikiran" wrote :
| Weird - maybe not :-)
|
If you bother to change the field name,
I think you can bother to change it as well in MC's xml descriptor. ;-)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212862#4212862
Reply to the post :
http://www.jb
"alesj" wrote :
| But this is "weird" custom behavior. :-)
Custom - yes. Weird - maybe not :-)
But i'll think a bit more to see if whatever i am trying to do is worth the
efforts :)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212859#4212859
Reply to t
"jaikiran" wrote :
| Maybe MC already has something to achieve this and i am not finding the
correct API?
BeanMetaDataBuilder::createContextualInject is the closest you can get.
But your example is different.
Current contextual injection would still need the property name,
it just wouldn't car
"alesj" wrote : The builder just builds metadata.
| Annotation's metadata population happens only in Describe state,
| as we know there that our CL exists == can do class info inspection.
|
Makes sense.
"alesj" wrote :
| I looks like you're actually trying to do what
AnnotationToBeanMe
The builder just builds metadata.
Annotation's metadata population happens only in Describe state,
as we know there that our CL exists == can do class info inspection.
I looks like you're actually trying to do what AnnotationToBeanMetaDataFactory
is meant for.
View the original post :
http://ww
