"rareddy" wrote : Adding the "isRuntime=true" did the trick, now I see
profile service invoking the bean correctly. Thank you.
|
Ok, good - btw... isRuntime will also fetch the new value of managedProperties with
ViewUse.Statistic when getValue() is called. Otherwise the value is set once
ManagementView is loaded, which is used for configuration properties.
"rareddy" wrote :
| I see that only beans that have @ManagementObject annotation + deployed through bean
deployer (thru -jboss-bean.xml) file are accessible through the profile service. Is there
a way I can build a bean with @ManagementObject annotation but initialized through
"new myBean()", some how injected into managed objects collection?
Hmm, this is difficult to say since i don't really know what you are trying to achieve
and the expected behavior for ProfileService. In general we create ManagedObjects based on
the attachment meta data in the deployers. So in case you have your own deployers you
should be able to explicitly add and expose your ManagedObjects, which is the preferred
way.
Maybe you want to briefly describe what you would like to do and how your integration code
works.
Thanks,
Emanuel
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265486#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...