Difference between revisions of "User:Mjb/Oracle XSLT processor bugs"
| Line 33: | Line 33: | ||
Example needed | Example needed | ||
| − | + | =Oracle XML DOM bugs= | |
| + | |||
| + | ==Document is an instance of Element== | ||
| + | |||
| + | I'm not entirely sure this is forbidden by W3C DOM, but it is counterintuitive. Saxon cannot be used to process an Oracle XML DOM Document because of it; Saxon is in the wrong for not using proper DOM node type attributes instead of "instanceof", but I think Oracle shouldn't be calling a Document an Element, either. | ||
Revision as of 03:32, 29 May 2006
I've had to use the Oracle XSLT processor twice: once in 2001, and once in 2005.
Both times, I ran into the same set of bugs which render this processor incompatible with other processors and basically not XSLT 1.0 conformant. At first it was amazing to me that these problems have not been fixed in all this time, but then I discovered that Oracle has the worst bug reporting and tech support system ever. It is basically impossible to file a simple bug report. So it's no wonder things never get fixed.
Here are the bugs:
Contents
- 1 Empty-string parameter sometimes tests true
- 2 Empty-string parameter sometimes causes crash
- 3 xml-stylesheet PIs are omitted from source tree
- 4 xsl:message output can corrupt XML or HTML result tree serialization
- 5 Last-modified date/time of importing stylesheet affects loading of imported stylesheets
- 6 xsl:when without a 'test' attribute is allowed
- 7 xsl:param in imported stylesheets not handled correctly
- 8 Oracle XML DOM bugs
Empty-string parameter sometimes tests true
Example needed
Empty-string parameter sometimes causes crash
Example needed
xml-stylesheet PIs are omitted from source tree
Example needed
xsl:message output can corrupt XML or HTML result tree serialization
Example needed
Last-modified date/time of importing stylesheet affects loading of imported stylesheets
Example needed
xsl:when without a 'test' attribute is allowed
Example needed
xsl:param in imported stylesheets not handled correctly
Example needed
Oracle XML DOM bugs
Document is an instance of Element
I'm not entirely sure this is forbidden by W3C DOM, but it is counterintuitive. Saxon cannot be used to process an Oracle XML DOM Document because of it; Saxon is in the wrong for not using proper DOM node type attributes instead of "instanceof", but I think Oracle shouldn't be calling a Document an Element, either.
