Here are my suggestions:
1. Incorporate modules/ha as the cluster solution into TC6
2. Keep modules/groupcom as a separate module
The reason I suggest a separate module, is cause it is a fairly
complex component and will have
a fairly large documentation base, it might be better to keep it
separate and have it
release separately from the core. That way, a busted IO component,
will not set back the tomcat release.
3. Storeconfig - this is Peter's baby and would be his choice.
I personally would suggest a rewrite of it and have a storeconfig
that is not dependent on the classes of tomcat,
ie, storeconfig today has one class for every component in tomcat,
so as soon as you swap out a component to a custom class,
there is no saving for that component anymore.
It could be equally easy to create a completely standalone
configuration tool.
But since I am not that familiar here,
I'd prefer to leave that decision to Peter if he has time to maintain
it in TC6.
Filip
Remy Maucherat wrote:
Remy Maucherat wrote:
Hi,
I think it's the right time to add the storeconfig code, as well as a
clustering implementation (so, which one ?).
Any new comments on this, 3 weeks later ?
I did put in place the necessary scripts and stuff for TC 6, so
releases could be made in the relatively near future as long as this
issue is resolved. I volunteer to do the release management, BTW.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
