Re: [Fwd: xml-security -> SVN?]

2005-10-13 Thread Davanum Srinivas
+1 from me. On 10/13/05, Berin Lautenbach <[EMAIL PROTECTED]> wrote: > Any preferences guys? What is below looks fine to me! > > Cheers, > Berin > > Original Message > Subject: xml-security -> SVN? > Date: Wed, 12 Oct 2005 20:22:45 -0400 (EDT) > From: Henri Yandell <[EMA

[Fwd: xml-security -> SVN?]

2005-10-13 Thread Berin Lautenbach
Any preferences guys? What is below looks fine to me! Cheers, Berin Original Message Subject: xml-security -> SVN? Date: Wed, 12 Oct 2005 20:22:45 -0400 (EDT) From: Henri Yandell <[EMAIL PROTECTED]> To: Berin Lautenbach <[EMAIL PROTECTED]> Hi Berin, Any thoughts on

DO NOT REPLY [Bug 36921] - (Websphere/Solaris) referecing org.apache.xpath.compiler.FunctionTable.m_functions throws java.lang.IllegalAccessError

2005-10-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 36921] - (Websphere/Solaris) referecing org.apache.xpath.compiler.FunctionTable.m_functions throws java.lang.IllegalAccessError

2005-10-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37075] New: - WINCAPI RSA Signatures Destructor ~WinCAPICryptoKeyRSA does not destroy key

2005-10-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: why would this code fragment cause XSec1.2.0 to leak memory?

2005-10-13 Thread Jesse Pelton
Nice work! That sure looks like a bug to me, and it's not fixed in CVS.   If you make the change you suggest, does it plug your leak? If so, I'd file a bug to make sure it gets attention. From: Cullum, Steve [mailto:[EMAIL PROTECTED] Sent: Thursday, October 13, 2005 8:39 AMTo:

RE: why would this code fragment cause XSec1.2.0 to leak memory?

2005-10-13 Thread Cullum, Steve
I think this may be the problem..inside the destructor ~WinCAPICryptoKeyRSA::CryptDestroyKey() never gets called.    I this is already fixed in the CVS release...sorry!!! to waste your time   WinCAPICryptoKeyRSA::~WinCAPICryptoKeyRSA() {     // If we have a RSA, delete it if (m_key ==

RE: why would this code fragment cause XSec1.2.0 to leak memory?

2005-10-13 Thread Cullum, Steve
Okay.. my memory leak seems to occur as soon as i call X509->clonePublicKey().   Calling prov->releaseSignature(sig) does not seem to release memory for the key.   The entire test driver that recreates the memory leak is shown.. I am basically doing what the documentations except i call the