Re: debugging

2010-01-11 Thread Sean Mullan
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.security=DEBUG, Console log4j.logger.org.apache.xml.security.test.AllTests=DEBUG, Console Specify the following system property wh

RE: debugging

2010-01-11 Thread Bolcina Ivan
Thanks, Sean. I dont have a clue, why it doesn't work. I put commons-logging.jar, commons-loggin-api.jar, log4j-1.2.15.jar into lib directory. I edited log4j.properties like below. Then I stared my app using java -Dlog4j.configuration=log4j.properties -jar PartnersXC.jar Still, nothing happen

Re: debugging

2010-01-11 Thread Sean Mullan
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, check my blog for info on configuring that: http://weblogs.java.net/blog/mullan/archive/2006/02/more_xml_sign

DO NOT REPLY [Bug 45095] log4j.properties in xmlsec sources and builds has side effects in production environment

2010-01-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45095 --- Comment #2 from adrian.b.rob...@gmail.com 2010-01-11 11:57:05 UTC --- Did this fix go into any releases? xmlsec-1.4.3.jar seems to be the latest and it has the problem described. -- Configure bugmail: https://issues.apache.org/bugzill

RE: debugging

2010-01-11 Thread Bolcina Ivan
Thanks Sean! That was it. Great blog! However,something strange is still happening, since app doesn't work without xmlsec jar. I guess JSR 106 (encryption is missing), JSR 105 is defined bouth in JDK and in this jar. BR,ivan -Original Message- From: sean.mul...@sun.com [mailto:sean.mu

Re: debugging

2010-01-11 Thread Sean Mullan
Bolcina Ivan wrote: Thanks Sean! That was it. Great blog! However,something strange is still happening, since app doesn't work without xmlsec jar. I guess JSR 106 (encryption is missing), JSR 105 is defined bouth in JDK and in this jar. Correct. Now, if you want to use a more recent Apache X

DO NOT REPLY [Bug 45095] log4j.properties in xmlsec sources and builds has side effects in production environment

2010-01-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45095 --- Comment #3 from sean.mul...@sun.com 2010-01-11 13:46:13 UTC --- (In reply to comment #2) > Did this fix go into any releases? xmlsec-1.4.3.jar seems to be the latest > and > it has the problem described. Here are the diffs for the fix