tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: [Proposal] Resurrecting storeconfig
Date Fri, 14 Dec 2012 17:26:54 GMT
On 14/12/2012 13:36, Remy Maucherat wrote:
> Hi,
> I would be willing to start maintaining again storeconfig, along with
> Jean-Frédéric.

Nice. That is a really useful feature. Great to see it (and you) back.

> So after a hiatus, we would be able to bring back this
> functionality which allows tweaking the configuration (through JMX in
> particular) and then saving it to server.xml and context.xml files to
> make changes survive a restart. On the downside, storeconfig in Tomcat
> will always remain an introspection based system prone to (very rare,
> hopefully) failures and some unhandled special cases, a artifact of
> Tomcat's rather freeform configuration files.

Indeed. As those issues appear we can look to see how best to address them.

> The proposal would be to move "storeconfig7/trunk" from the sandbox to
> "modules/storeconfig" in the Tomcat 7 branch [a port to trunk, aka
> Tomcat "8", would be coming shortly, since I believe its container API
> would now start to be more stable].

Merging Engine and Service are still on the Tomcat 8 TODO list but I'm
increasingly coming to the view that it isn't worth doing. It would
break lots of existing stuff and the benefit of the merge is marginal.
The other largish looking changes (e.g. web.xml parsing) shouldn't
impact much / at all on StoreConfig.

How far away is the trunk version?

> I don't recall Tomcat 6 having
> modules, so I don't see where storeconfig6 would live there, and as a
> result I propose leaving it in the sandbox.

We could create a modules in tc6.0.x/trunk

One of your changes that I have really come to appreciate over the years
is the single source tree. What was your reasoning for adding it in
modules rather than the main source tree?

> One issue I'm wondering about is the build system. After all that time,
> I've starting using Maven instead of Ant (unbelievable, I know ...), and
> while I am fine continuing using existing Ant build systems, I find
> adding ones to newer components quite useless.

It shouldn't be too hard to add another JAR to the existing Ant build.
Once the code is in place, I'm happy to take a look.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message