Hello Igor, Thank you for the quick reply. However, the problem is still there because the xerces code contains calls to system functions that are not allowed by wack certificate. One example is the function getenv() that is used in one place, but there are several other calls to functions that access the registry and are not allowed. Those functions are present in the files mentioned in the previous email.
Best regards, Marius Cojocaru On Oct 28, 2017 15:33, "Igor Toujilov" <name1390453...@mail.com> wrote: > Hi Marius, > You can take the Xerces source code, create a Windows DLL project from it, > add required features like a WACK certificate, and compile it. > > Cheers, > Igor > > > > Sent: Friday, October 27, 2017 at 1:30 PM > > From: "Marius Cojocaru" <mariusade...@gmail.com> > > To: c-users@xerces.apache.org > > Subject: Xerces DLL WACK validation for windows store application > > > > Hello, > > > > My name is Marius Cojocaru and I am using xerces 3.1 succesfully on a > > company project. > > Common code is used to compile the project on linux and windows for > > building an API. > > A request has been made to support windows applications (windows 8.1 SDK) > > and I am not able to validate the xerces DLLs for that purpose. > > There are a lot of unsupported calls from Win32TransService and > > Win32MsgLoader. > > I tried using xerces 3.2 as well but the same issues are found. > > Do you know if it is even possible to create a WACK certified dll for > > apache Xerces or should I move to using native parsers like System.xml > (or > > MSXML or XMLLie) on windows 8.1 sdk. > > > > Best regards, > > Marius Cojocaru > > >
