Yes, I plan to - but if you have nothing else to do :-), or this is a blocker - please look into it as well.
By 'optimizations' I mean: - using dynamic mbeans ( are lighter, I don't think we gain much by using model mbeans ) - lazy as much as possible - improve MBeansSource, add saving - to read/write mlet-style config fragments - check where we use JMX directly, add wrappers in modeler - ( probably in sandbox ): implement a modeler version that doesn't actually use JMX, for lighter containers. The tomcat code is using mostly Registry, so it should not require a lot of changes. Obviously, most of the other APIs will be broken - but we are in a separate package than commons.modeler, so it shouldn't be a problem. In any case - this should not block Tomcat6 release in any way, I'll use a separate package until it is stable, and it can get in a 6.1 or 6.2 if needed. Costin On 5/5/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:
Costin Manolache wrote: > fix modeler BTW, do you plan to do the modeler optimizations, or should I plan to look into that ? Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
