This is precisely what I needed to know. Thank you very much! I could use MSXML. I'm not sure whether I can justify the effort to investigate an alternative that takes more work to get started. The search of the open source space is being driven "bottom up", not top down from management. An open source solution could have some advantages to the organization. If I end up using Xerces I will certainly communicate that to the Xerces developers.
Thanks, Mark Delaney -----Original Message----- From: Alberto Massari [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 28, 2005 3:36 AM To: [email protected] Subject: Re: How stable is the COM wrapper? Hi Mark, the COM code compiles, but it hasn't been improved since long ago; we got the feeling that nobody was using it, so we were thinking about deprecating it. So get a source distribution of Xerces and compile it (there is a project for it inside the Visual C++ workspace), and let us know if it does what you need. Knowing that someone uses it is important to us. Thanks, Alberto At 12.28 27/06/2005 -0700, Mark Delaney wrote: >I want to pass XML nodes from one Windows program to another without >passing megabytes of BSTR from here to there. I am investigating >open source alternatives to Microsoft's MSXML for an environment >using DevStudio on Windows XP SP2. > >There is mention in the Xerces build instructions for how to create >a COM wrapper for the Xerces 2.6.0 DOM implementation. This sounds >like what I want. > >Googling around on this, I found one email on a list somewhere a >couple of years old that suggested that the COM wrapper was going to >be deprecated shortly. But it still seems to be there, and there are >more recent fixes checked in in the bug database. But it is not part >of the binary distribution. > >I need to know if this COM wrapper is a living supported stable >solid part of the Xerces 2.6.0 DOM implementation. If so, it is >probably just what I am looking for. Alternately, are there any >other alternatives I should be looking at that would be a viable >open source alternative to MSXML's COM interfaces? > >Thank you! > > >Best regards, > >Mark Delaney > > >(My opinions are my own. Please do not confuse them with my >employer's opinons.)
