Mailing-List: contact security-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: security-dev@xml.apache.org
From: bugzilla@apache.org
To: security-dev@xml.apache.org
Subject: DO NOT REPLY [Bug 44863] Improved logging in signature handling
In-Reply-To: <bug-44863-6260@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20080423232605.2E7BE234C0FF@brutus.apache.org>
Date: Wed, 23 Apr 2008 16:26:05 -0700 (PDT)

https://issues.apache.org/bugzilla/show_bug.cgi?id=44863


--- Comment #3 from sean.mullan@sun.com  2008-04-23 16:26:04 PST ---
(In reply to comment #2)

> Adding the logging to the OutputStream classes does have one drawback, though. 
> Especially for the reference logging, I believe you lose the URI so in
> situations where multiple references are present you have to figure it out. 
> Granted, this is most likely not difficult, but it is helpful.  We tend to like
> to have as much info as possible as long as there is no significant performance
> impact.  That being said, I'll take whatever I can get.  Thanks.

If you enable logging at the debug level, all the builtin resolvers log a
message "I state that I can resolve reference: "uri"", and a few logging
messages later the pre-digested bytes will be logged (after I put in the fix).


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.