It might be useful if you told us what the alleged problem is. There are
cases where different processors can legitimately produce different
output and still be conformant to the spec.
If it really is a non-conformance, there is little anyone on this list
can do to help: it's an issue between you and your software supplier.
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
cknell(_at_)onebox(_dot_)com
Sent: 02 January 2003 15:22
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] Problems with Oracle XSL processor
I am having a problem with the Oracle XSLT processor. It
fails to output nodes that it ought to output using a
stylesheet I have written. Using the same source document and
stylesheet, I have tested the MSXML, Xalan-J, and Instant
Saxon processors. All produce the tree I expect with all
nodes where I expect them. Oracle's transformer fails in a
big way. I have been in touch with Oracle's support, but they
seem mainly interested in dodging the issue of what I believe
to be a defect in their processor rather than addressing the matter.
Has anyone else used Oracle's processor extensively and if
so, what gimmicks do I need to use to work around its shortcomings?
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list