On Mon, 29 Jul 2002, Craig R. McClanahan wrote: > > As long as we are using modeler - I think we shouldn't have to write > > _any_ custom MBean. > > > > I look forward to seeing how you plan to deal with some of the interesting > cases -- everything from the "users" MBean attribute on the > MemoryUserDatabase MBean to synthesized MBeans like MBeanFactory that > don't really correspond to any Catalina component, but are there only for > JMX clients to use.
Ok, let me try again: we shouldn't use both modeler and 'custom' mbean at the same time. For 'intersting' cases we can use a custom standard mbean or a dyanmic mbean or even a custom model mbean. I don't understand MBeanFactory very well - my understanding is that you can declare a 'class' and have the constructor called ( that's why the constructor is defined in JMX ), so the factory is redundant. But it may be a cleaner way to construct elements. I don't know how it can deal with 'custom' modules ( like user-defined realms or connectors ). For users - given the performance and scalability implications it certainly need a custom mbean, if we go with one mbean per user model. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
