 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Rolf Fox Guest
|
Posted: Thu Apr 06, 2006 8:03 pm Post subject: Using MSXML 6.0 with TXMLDocument |
|
|
What are my options for getting TXMLDocument
to use the newest version of MSXML that is
installed on the machine, up to and including
6.0?
I noticed that CreateDOMDocument() tries to
use the newest MSXML up to 4.0, as follows:
line 483: msxmldom.pas
Result := TryObjectCreate([CLASS_DOMDocument40, CLASS_DOMDocument30,
CLASS_DOMDocument26, msxml.CLASS_DOMDocument]) as IXMLDOMDocument;
I guess all that needs to change is to add
CLASS_DOMDocument60 to the array of GUIDs.
Even though I'm using BDS 2006, it seems that
TXMLDocument is not as up-to-date as it could be.
I'd prefer to stick with using TXMLDocument as
as I quite like its features and flexibility.
Do I have to modify XMLDoc.pas myself and build
and reinstall the corresponding package?
Thanks,
Rolf Fox. |
|
| Back to top |
|
 |
Bruce McGee Guest
|
Posted: Sat Apr 08, 2006 6:03 pm Post subject: Re: Using MSXML 6.0 with TXMLDocument |
|
|
It looks like it will probably work. XMLDocument uses the
IXMLDOMDocument interface and ignores the differences in
IXMLDOMDocument2 and IXMLDOMDocument3. In case you haven't already
seen it, here's the GUID:
CLASS_DOMDocument60: TGUID = '{88D96A05-F192-11D4-A65F-0040963251E5}';
Give it a shot and see what happens.
Out of curiosity, what are some of the things you like about TXMLDoc?
I use IXMLDOMDocument2 directly and don't know what I might be missing.
--
Regards,
Bruce McGee
Glooscap Software |
|
| Back to top |
|
 |
Rolf Fox Guest
|
Posted: Thu Apr 13, 2006 5:03 pm Post subject: Re: Using MSXML 6.0 with TXMLDocument |
|
|
Oh, you're not really missing that much. I
used the IXMLDOMDocument directly until I
upgraded to BDS 2006 and discovered the
TXMLDocument parser wrapper.
But I liked how I had my choice of a number
of XML engines through the DOMVendor property.
If in the future I have some compelling
reason to switch to the OpenXML or Xerces parser,
it will be easy to change.
One thing that made switching to TXMLDocument
easy was that I could cast into the interface
and extract the underlying IXMLDOMDocument.
I didn't have to rewrite any of my code that
uses the IXMLDOMDocument interfaces.
It also gives access by means of the Events
tab on the Object Inspector to the DOM events.
I could never get the MSXML DOM events to work
when I used the IXMLDOMDocument interface set
directly, so I was pleased to see how easy the
TXMLDocument made things.
Rolf Fox. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|