We probably should! I suspect we need to check the exception type and
either re-throw it or (if a memory error) wrap it.
Cheers,
Berin
Milan Tomic wrote:
Berin,
I have noticed that when some exception (e.g. "Error obtaining default
PROV_RSA_FULL") occur in ctor of some XSEC class (e.g.
WinCAPICryptoProvider::WinCAPICryptoProvider()) than it is being wrapped
into "out of memory exception" (throw XSECException
(XSECException::MemoryAllocationFail);) by XSECnew macro. Can/should we
improve this (somehow)?
Best regards,
Milan
