Drop container logging in idp-tomcat|jetty-base

[Tom Zeller]

Actually, I’m thinking we should drop container logging from the java-idp-jetty|tomcat-base examples (and therefor the Windows Installer).

Reasons are, (a) I don’t have an env to test Tomcat + SLF4J performance, and (b) Jetty still writes to its default logger (as defined in etc/jetty-logging.xml, we could override) unless the location of the Logback configuration File is supplied when starting (-Dlogback.configurationFile=...) _and_ we resolve the SLF4J multiple bindings warning (e.g. by sending to /dev/null dunno).

So, pending discussion/objection, I think it’s best to only do Logback access/request logging for Tomcat and Jetty (that at least seems straightforward).

Tom