Thank you for quick answer. And one more question:
1. Custom components. Did you mean components wich are not in standard Tomcat compilation? On 23 March 2010 18:24, Mark Thomas <ma...@apache.org> wrote: > On 23/03/2010 16:09, Sergy Pylypchuk wrote: > > Hello! > > I'm developing utility for remote Tomcat 6.0.x configuration via JMX > MBeans. > > But I figured out some issues: > > > > 1. There is no Catalina:type=StoreConfig MBean and I'm not able to > persist > > configuration. I found this > > https://issues.apache.org/bugzilla/show_bug.cgi?id=42708 bug. And now > I'm > > going to port StoreConfig from Tomcat 5.5. > > So, I what to ask you: what kind of problems will I face during > > implementation? > > 1. Custom components. > 2. Differentiating between defaults and values that were actually set. > > > 2. And second issue is connected to previous one. There are no MBeans for > > cluster configuration in Tomcat 6.0.x. (See mail list archive: > > http://www.mail-archive.com/us...@tomcat.apache.org/msg32974.html). So, > is > > it the only one reason why StoreConfig was not ported to Tomcat 6? > > No. It was hard to maintain and not that many folks were interested in > maintaining it. > > > And are there any ideas how to implement cluster managing via JMX? > > Follow the standard pattern used by the other components > > > Can I try to port MBeans from Tomcat 5.5? > > It is a starting point. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
