Hi Tapestry-users, Tapestry's AbstractReloadableObjectCreator, LoggingInvokableWrapper, ModuleImpl, RegistryImpl and others log a lot of really boring stuff. For some of our tests it's actually the majority of the log output making it difficult to visually parse what's going on in the application. Unfortunately they use the application loggers ie the category of the log entry is always the class they are doing stuff to and not their own class so I can't turn off their logger without turning off the application logging.
This happens with Tapestry 5.3.6 and log4j 1.2. Is there any workaround on the tapestry side because I don't see how I can filter these log entries via log4j? Thanks for your help in advance! Best Regards, Wulf
