<<I need to have a better integration between Avalon and JMX but because there are some overlaps I want to solve them elegantly. I know that the attached code is very primitive but its purpose is only to get a better feedback.>>
I'm sorry to take so long in responding...I've installed windows for the 4th time in two weeks now and it still keeps hanging, and linux still chokes on my DSL connection (or rather, my ISP chokes on linux...) << So, my questions are: a) Is this MBeanComponentManager the right approach (eventually the MBeanComponentSelector too...when I'll understand more about the framework...maybe when Berin's docs will be done)?! >> I personally have my doubts about the entire concept of an MBeanComponentManager (see the archive), but this is probably because I'm still too unused to using a ComponentManager. I'll try and find time this sunday to finally finish up the mess I left JMX within phoenix in. << b) Did you have in mind federated component managers that will register/lookup the components with JNDI contexts and/or JMX server-s in a consistent way? >> I'm not sure, but this sounds more like an app to run on top of phoenix (or beside it) and not like a phoenix core capability. There's been talk 'bout this before. I for one have nothing against it. To cut a long story short, we're not quite sure yet about how to handle JMX w/ phoenix. Input is welcome =) regards, Leo, who really hopes he'll be able to send this out... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
