Not that I know of. The log4j configurators are singletons, so I don't know how you could have multiple 'congurations' in the same JVM. It'd be a good question for the good folks on log4j proj if you don't get a satisfactory answer here.
You could, using your own known categories, assign those categories to specific appenders (which could then be directed to their own respective files). It's not as flexible (per-deploy-configurable) as you seem to want, but it'll get you close.
We have a convention by which categories are based on our package names, so output granularity (and method) is controlled by pkg.
Thank you for the information.
I had a feeling that would be the case. However, I do wonder (as I don't have direct experience) how people get Tomcat to handle separate log4j configuration for its installed web apps.
If anyone has experience doing this, can you please tell me how? I doubt Tomcat starts a JVM for each web app...