I just had a look at this issue. The exception is in fact logged twice. Once by Digester and once by us. I changed our log statement to a warning and it now doesn’t contain the stacktrace any more. I think that should be OK.
Unfortunately there is no way for us to silence the Digester log statement. That has to be done by the users in their logging configuration. But as we are shading Digester into our JAR with a custom package name it should be OK to do so. Just disable logging for “com.ocpsoft.shade.org.apache.commons.digester.Digester”.
For PrettyFaces 4.0 the situation is much more simple as we are using JAXB directly. I changed the logging statement so it won’t be so noisy as before.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.