On Mon, 29 Jul 2002, Craig R. McClanahan wrote: > > The only place that will prove difficult is when a component's method > implementing an operation wants an object instead of a String or primitive > (say, Container.addChild()). We also have the choice (in Tomcat 5) to > break the existing APIs a little bit more freely, which I didn't believe > we could really do in 4.1.
No problem - just add (in the component implementation) a second method taking a string as parameter. That's how jk works - each jk component has a name, and 2 setters ( one taking a string ). Again, no interface change is needed - the config setters are specific to the implementation object. ( same as in commons-logging :-) > That's a good idea -- it will reduce the need to write custom MBean > implementations without eliminating the opportunity to do so when it's > helpful. As long as we are using modeler - I think we shouldn't have to write _any_ custom MBean. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
