I attended the LAJUG presentation of Kitty.  Not sure who may have written in 
before, but I will do my best to summarize some of the thoughts that came out 
of the presentation.

* Several of us liked the idea of a command line JMX tool independent of the 
tool you are building to make administering tomcat prime time.
* I suggested making Kitty into a pluggable architecture where the tomcat 
specific groovy scripts are just a plug in used by your command line JMX tool.  
This would require some pluming work to be done and forethought into how one 
would plug into the tool.  This opens the door for a separate Tomcat 6 and 
Tomcat 7 plugs.  JVM JMX general stuff could be another plug-in.  This type of 
architecture would allow users of the tool to write their own plugs for their 
own specific needs depending on the Tomcat environment they are running.  It 
also opens the door for people to build or contribute plug-ins not even related 
to Tomcat.
* I would also suggest spending some time thinking about how users could 
override and extend some of the functionality that you have for administering 
Tomcat.

These are my thoughts and seemed to be shared by others that where at the 
presentation.  I hope you find some value in them.

Cheers,
- Ken

Kennett Dempster
Senior Software Engineer
Sony Network Entertainment, Inc. Los Angeles
310-981-1827

Reply via email to