Mladen Turk wrote:
3. Get rid of Jk2* from Apache module and use only 'Jk2On' That will register the JK2 in the same way as filter on IIS (for each virtual server).
All this imply that the workers2.xml is the main config point, meaning that
the same workers2.xml is operable either on IIS or Apache or any other web
server. Also there are no other 'per-server' directives rather then 'on or
off'.
If you're proposing getting rid of JkUriSet, DON'T!
It is *very* helpful to be able to mount URI's for a specific web app in an Apache .conf file that contains all the other settings for that web app. This is doubly true when you want that single conf file to cover mod_jk and mod_jk2 bases so you can quickly and easily toggle between the two in case of issues.
Having to merge per-web-app configurations into a single XML file would be a mess by comparison for such use cases....
-- Jess Holle
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
