Wally Dennis wrote:
Update:
I decided to try to enable the JDK Logging facility to run in parallel
with Log4j, since in theory there should be no conflicts. However, when
I follow the instructions contained in the blog postings for how to
configure the logging, I still do not get any output. When I debug
through the XML Security code, I am definitely calling the
org.apache.xml.security.utils.DigesterOutputStream class instead of the
org.jcp.xml.dsig.internal.DigesterOutputStream class. Am I missing
something? The log statements are definitely not present in the former
version of this class - should they be or is there a reason why
WSS4J/Rampart is using the version without the logging capability?
There are 2 APIs in Apache XML Security: the standard JSR 105 API, and
the non-standard Apache XML Security API. Depending on which one you are
using, some of the code paths are different. For example, if you use JSR
105, the code in org.jcp.xml.dsig.internal will be used whereas it will
not be if you are using the Apache API. It sounds as if you are not
using JSR 105, thus you aren't getting the log messages from the
org.jcp.xml.dsig.internal classes. But you should be seeing some other
messages?
--Sean
