In the Tuscany project we recently ran into a problem with logging inside Tomcat where all container messages were being suppressed. One of the contributory factors involved was that log4j was getting configured by the log4j.properties file inside policy-1.0.jar
As a library jar, I don't think policy should be configuring log4j itself but should work within the setup of whoever is using it. Including this file opens the risk of messing up the user's logging setup (which is what happened to us). Is there some specific setup needed for policy or would it be possible to remove this file from inside the jar (perhaps for the 1.0.1 release)? Thanks -- Jeremy
