o:sean.mul...@sun.com] Sent: Monday, January 11, 2010 8:47 PM
To: security-dev@xml.apache.org Subject: Re: debugging
Are you using the JSR 105 API and JDK 6? If you are, it could be
using the XML Security implementation bundled with JDK 6. This uses a
different logging mechanism (JDK logging). If so
n.com [mailto:sean.mul...@sun.com]
Sent: Monday, January 11, 2010 8:47 PM
To: security-dev@xml.apache.org
Subject: Re: debugging
Are you using the JSR 105 API and JDK 6? If you are, it could be using
the XML Security implementation bundled with JDK 6. This uses a
different logging mechanism (JDK logging).
n
and then I started my app.like
-Original Message-
From: sean.mul...@sun.com [mailto:sean.mul...@sun.com]
Sent: Monday, January 11, 2010 5:10 PM
To: security-dev@xml.apache.org
Subject: Re: debugging
Look at src/org/apache/xml/security/resource/log4j.properties in the
source tree. Ch
sean.mul...@sun.com [mailto:sean.mul...@sun.com]
Sent: Monday, January 11, 2010 5:10 PM
To: security-dev@xml.apache.org
Subject: Re: debugging
Look at src/org/apache/xml/security/resource/log4j.properties in the
source tree. Change these lines to print debug messages on Console:
log4j.logger.org.apache.xml.sec
properties?
BR,ivan
-Original Message-
From: sean.mul...@sun.com [mailto:sean.mul...@sun.com]
Sent: Wednesday, January 06, 2010 3:27 PM
To: security-dev@xml.apache.org
Subject: Re: debugging
Bolcina Ivan wrote:
Hi.
How to enable debuging messages. I looked at log4j.log and it seem
ation
files/startup properties?
BR,ivan
-Original Message-
From: sean.mul...@sun.com [mailto:sean.mul...@sun.com]
Sent: Wednesday, January 06, 2010 3:27 PM
To: security-dev@xml.apache.org
Subject: Re: debugging
Bolcina Ivan wrote:
> Hi.
>
>
>
> How to enable debuging m
Bolcina Ivan wrote:
Hi.
How to enable debuging messages. I looked at log4j.log and it seems
fine, but no debug messages are printed out to console?
See: http://commons.apache.org/logging/guide.html#Configuration
--Sean
Andrew,
Fix is in CVS.
With thanks!
Cheers,
Berin
Berin Lautenbach wrote:
Andrew,
DSIGREference::createBlankReference executes
ret->setAttribute(MAKE_UNICODE_STRING("type"),with a lower case 't' on
"type".
Ouch. You are absolutely correct - this should be an upper case 'T'. I
will
Andrew,
> DSIGREference::createBlankReference executes
> ret->setAttribute(MAKE_UNICODE_STRING("type"),with a lower case 't' on
> "type".
Ouch. You are absolutely correct - this should be an upper case 'T'. I
will check a fix into CVS tonight.
> Being a newbie, is this the proper way to report
I figured out my debugging problem and what I discovered I believe is a bug in
the XSec DSIGReference.cpp
Here is the situation:
DSIGREference::createBlankReference executes
ret->setAttribute(MAKE_UNICODE_STRING("type"),with a lower case 't' on "type".
However in DSIGReference::load
else if (st
10 matches
Mail list logo