[Bulk] Re: [Bulk] Re: [xmlsec] ErrorsCallback ???

[Edward Shallow]

Hi Aleksey,

   Thanks once again. The following worked when added to the ErrorsCallback
(mscrypto only) ...

    errCode = win32api.GetLastError()
    errMsg = win32api.FormatMessage(errCode)

Ed 

-----Original Message-----
From: xmlsec-bounces at aleksey.com [mailto:xmlsec-bounces at aleksey.com] On
Behalf Of Edward Shallow
Sent: January 6, 2006 12:07 PM
To: xmlsec at aleksey.com
Subject: RE: [Bulk] Re: [Bulk] Re: [xmlsec] ErrorsCallback ???

 Oh I see. You mean the Windows Win32::GetLastError() call. I do not mind
trying this as a work-around. I'll let you know. I think the ideal would be
to normalize the error handling as you suggested.

Thanks,
Ed

-----Original Message-----
From: xmlsec-bounces at aleksey.com [mailto:xmlsec-bounces at aleksey.com] On
Behalf Of Aleksey Sanin
Sent: January 6, 2006 12:00 PM
To: ed.shallow at rogers.com
Cc: xmlsec at aleksey.com
Subject: [Bulk] Re: [Bulk] Re: [xmlsec] ErrorsCallback ???



> The xmlGetLastError seemed very attractive and it does work perfectly 
> for all libxml2 calls and returns output which is identical to stderr.

The message on std err from xmlsec is printed by LibXML2. I can not test it
on Windows at the moment, but I can get back all this information using
xmlGetLastError() on Linux.


As I wrote you before, the "extra" information you see is provided from
*system* GetLasstError() call. You can make same call from python inside
your error callback.


Aleksey

_______________________________________________
xmlsec mailing list
xmlsec at aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec


_______________________________________________
xmlsec mailing list
xmlsec at aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec