I think you should rely on Ant scripts for reloading of that kind of relatively complex situations.
Unfortunately, my context is much more complicated. I can't use the manager or ant (at this step of what I could guess) because they are rewriting (sometimes) the server.xml without taking car of my CoyoteConnector setup (which is hosted in an entity).
Is this really needed ? Many (most) context related container configuration stuff can be put in context files.
Reloading server.xml is not supported without restarting the whole server, and there's the possibility of messing with the config and breaking things. These were the reasons why the context files were introduced in the first place.
So...
Clearly, here, they are filtering virtual hosts through a single web application. So, I don't want to have a auto-deploying context in al the hosts because I don't know what would be the tomcat behaviour in such a situation.
There's no concurrency when reloading webapps (by default, one thread per engine for all recurrent tasks, including reloading, auto deployment, session expiration, etc) so it could work well enough.
-- xxxxxxxxxxxxxxxxxxxxxxxxx R�my Maucherat Developer & Consultant JBoss Group (Europe) S�RL xxxxxxxxxxxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
