The packages com.ms.xml.xmlstream and the alternate version are functionally
equivalent, but the Windows-specific one has much higher performance. Choose
portable or fast depending on your needs.
--Andrew Layman
AndrewL@microsoft.com
> -----Original Message-----
> From: Don Park [SMTP:donpark@quake.net]
> Sent: Friday, November 14, 1997 11:16 AM
> To: Joe Lapp; xml-dev@ic.ac.uk
> Subject: Re: MSXML is tied to Windows
>
> Joe,
>
> Windows dependency of MSXML is minimal. All you have to do is following:
>
> 1. remove com.ms.xml.dso package.
>
> Delete the class files from the jar and/or comment it out of the makefile.
> DSO is accessed by some of the samples but none of the other MSXML
> packages.
>
> 2. remove dependency on com.ms.xml.xmlstream package.
>
> Latest version of MSXML includes an alternate XMLInputStream class located
> inside the 'make' directory. Replace com.ms.xml.util.XMLInputStream with
> the alternate version to remove dependency on com.ms.xml.xmlstream
> package.
>
> WIth above two changes, you will end up with a pure-Java version of MSXML.
> MSXML is the most complete XML parser available right now and you get the
> source code on top of it. I would be smiling by now if I were you :-)
>
> Don Park
>
> -----Original Message-----
> From: Joe Lapp <jlapp@acm.org>
> To: xml-dev@ic.ac.uk <xml-dev@ic.ac.uk>
> Date: Friday, November 14, 1997 11:02 AM
> Subject: MSXML is tied to Windows
>
>
> >I've been looking at Microsoft's MSXML. Although it is written
> >in Java, it is tied to the Windows platform. Instead of using
> >Java's URL facilities in java.net.*, it provides an ActiveX
> >control to do the job. Class com.ms.xml.util.XMLInputStream
> >relies on COM interface IXMLStream, which MSXML provides as a
> >DLL written in C++ (see com\ms\xml\XMLStream\XMLURLStream).
> >
> >I'm looking for a 100% pure Java XML parser that is being
> >actively maintained. I've got a few projects up my sleeve,
> >and I want to be sure that the code I write is cross-platform.
> >If I write to MSXML, I tie myself into Microsoft's API. Given
> >that the only implementation of that API works only on Windows,
> >to write to MSXML would be to tie my Java tool to Windows.
> >
> >It seems that Microsoft has the most complete implementation
> >of an XML parser, so Microsoft is doing a very good job of
> >trying to get me to write Java that works only on Windows.
> >--
> >Joe Lapp (Java Apps Developer/Consultant)
> >Unite for Java! - http://www.javalobby.org
> >jlapp@acm.org
> >
> >xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
> >Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> >To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
> >(un)subscribe xml-dev
> >To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
> message;
> >subscribe xml-dev-digest
> >List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
> >
> >
>
>
> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
> message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)