This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Saxon and jvm
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: Saxon and jvm
- From: Joshua Allen <joshuaa at microsoft dot com>
- Date: Sun, 13 Aug 2000 12:41:31 -0700
- Reply-To: xsl-list at mulberrytech dot com
I always got that in IE5 as well -- you get that when you do not point saxon
to a different parser, such as xerces. I can only imagine that when you
were using saxon before, stderr was somehow being redirected? In any case,
I would think it is correct from Saxon's point of view for you to get that
message when you are not specifying a different parser; if you were not
getting it before, it was probably a config problem or a bug.
> -----Original Message-----
> From: Dave Pawson [mailto:daveP@dpawson.freeserve.co.uk]
> Sent: Sunday, August 13, 2000 1:14 AM
> To: xsl-list@mulberrytech.com
> Subject: Saxon and jvm
>
>
> If my understanding is right, Saxon gets its jvm
> from ie5 by default?
>
> I just installed ie5.5 and instant saxon comes
> back at me with
> Cannot find ParserManager.properties - using built-in parser
>
> Prior to 5.5 install this had never occurred. Has something
> changed in IE5 to make it invisible?
>
> Anyone else come across this... and does it matter?
> Aelfred is, I think, the built-in parser?
>
> TIA DaveP
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list