Hello, We also had the same problem but apparently they can be solved without changes from the Tapestry side.
You can modify your dependencies in your pom.xml (I assuming you are using maven) that tapestry and any tapestry dependency will not include commons-logging jars in the WAR file, and include SLF4J commons-logging integration to the WAR file as a direct dependency. It would be off course simpler to have tapestry change its dependencies but it's hard to reason about commons-logging to people that never had a problems with that. Renat On 26/06/07, Michael Grundvig <[EMAIL PROTECTED]> wrote:
Is there a way to get commons-logging out of tapestry? I just fought with it yet again the other day. Maybe a move to something like SLF4J? Commons logging is really frustrating with it's classloader disaster always waiting in the wings. The most comprehensive set of arguments against it are found here: http://www.qos.ch/logging/classloader.jsp And more details on SLF4J here: http://www.slf4j.org/ Personally, I prefer SLF4J quite a bit but I'd be happy with pretty much anything other then commons-logging. Even many of the new Apache projects are leaving it behind. Thanks! Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Best regards, Renat Zubairov --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
