You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Rick Tessner <ri...@dingle.myra.com> on 2000/07/18 23:00:15 UTC
Docbook XSL w/ Xalan 1.1 : "XSLProcessorException unknown axis: 29"
Hi All!
I'm using Xalan-J and Xerces-J via Cocoon (1.7.4) and have XML
documents written using the Docbook XSL (currently using version 1.15
of the Docbook XSL)
I'm wanting to upgrade to Xalan-J 1.1 (and Xerces-J 1.1.2), but I'm
getting xalan.xslt.XSLProcessortExeption errors with the newer
Xalan.
Everything works just fine with Xalan-J 1.0.1 (with Xerces-J 1.0.3).
I did notice on the bug list for Xalan that there is a known problem with
"Complex XPath expressions including steps after a union raise an unknown
access error and do not return the correct node-set." [ Taken from
the Xalan Release Notes page ]
Would this be related to that issue?? Is there a work-around for this??
Is anyone out there using Docbook XSL and Xalan-J 1.1??
A long stack trace from Cocoon follows ...
org.apache.xalan.xslt.XSLProcessorException: pattern = '($node/docinfo
|$node/chapterinfo
|$node/appendixinfo
|$node/prefaceinfo |$node/bookinfo
|$node/setinfo |$node/articleinfo
|$node/artheader |$node/sect1info
|$node/sect2info |$node/sect3info
|$node/sect4info |$node/sect5info
|$node/refsect1info
|$node/refsect2info
|$node/refsect3info
|$node/bibliographyinfo
|$node/glossaryinfo |$node/indexinfo
|$node/refentryinfo |$node/partinfo
|$node/referenceinfo)[1]' unknown axis: 29
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at org.xml.sax.SAXException.(SAXException.java:45)
at org.apache.xalan.xpath.XPathException.(XPathException.java:92)
at org.apache.xalan.xslt.XSLProcessorException.(XSLProcessorExcep
tion.java:90)
at org.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java
:1630)
at org.apache.xalan.xslt.XSLTEngineImpl.error(Compiled Code)
at org.apache.xalan.xslt.XSLTEngineImpl.process(Compiled Code)
at org.apache.cocoon.transformer.XalanTransformer.transform(Compi
led Code)
at org.apache.cocoon.processor.xslt.XSLTProcessor.process(XSLTPro
cessor.java:110)
at org.apache.cocoon.Engine.handle(Compiled Code)
at org.apache.cocoon.Cocoon.service(Cocoon.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnectio
n.java:317)
at org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java:479)
---------
org.apache.xalan.xpath.XPathException: pattern = '($node/docinfo
|$node/chapterinfo
|$node/appendixinfo
|$node/prefaceinfo |$node/bookinfo
|$node/setinfo |$node/articleinfo
|$node/artheader |$node/sect1info
|$node/sect2info |$node/sect3info
|$node/sect4info |$node/sect5info
|$node/refsect1info
|$node/refsect2info
|$node/refsect3info
|$node/bibliographyinfo
|$node/glossaryinfo |$node/indexinfo
|$node/refentryinfo |$node/partinfo
|$node/referenceinfo)[1]'
unknown axis: 29
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at org.xml.sax.SAXException.(SAXException.java:45)
at org.apache.xalan.xpath.XPathException.(XPathException.java:92)
at org.apache.xalan.xpath.XPath.error(XPath.java:1562)
at org.apache.xalan.xpath.SimpleNodeLocator.union(Compiled Code)
at org.apache.xalan.xpath.XPath.union(XPath.java:851)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xpath.XPath.group(Compiled Code)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xpath.SimpleNodeLocator.findNodeSet(SimpleNod
eLocator.java:1113)
at org.apache.xalan.xpath.SimpleNodeLocator.step(Compiled Code)
at org.apache.xalan.xpath.SimpleNodeLocator.locationPath(Compiled
Code)
at org.apache.xalan.xpath.XPath.locationPath(Compiled Code)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xpath.XPath.execute(Compiled Code)
at org.apache.xalan.xslt.ElemVariable.getValue(Compiled Code)
at org.apache.xalan.xslt.ElemVariable.execute(Compiled Code)
at org.apache.xalan.xslt.ElemTemplateElement.executeChildren(Comp
iled Code)
at org.apache.xalan.xslt.ElemTemplate.execute(ElemTemplate.java:1
45)
at org.apache.xalan.xslt.ElemCallTemplate.execute(ElemCallTemplat
e.java:140)
at org.apache.xalan.xslt.ElemTemplateElement.executeChildren(Comp
iled Code)
at org.apache.xalan.xslt.ElemLiteralResult.execute(Compiled Code)
at org.apache.xalan.xslt.ElemTemplateElement.executeChildren(Comp
iled Code)
at org.apache.xalan.xslt.ElemLiteralResult.execute(Compiled Code)
at org.apache.xalan.xslt.ElemTemplateElement.executeChildren(Comp
iled Code)
at org.apache.xalan.xslt.ElemTemplate.execute(ElemTemplate.java:1
45)
at org.apache.xalan.xslt.StylesheetRoot.process(Compiled Code)
at org.apache.xalan.xslt.XSLTEngineImpl.process(Compiled Code)
at org.apache.cocoon.transformer.XalanTransformer.transform(Compi
led Code)
at org.apache.cocoon.processor.xslt.XSLTProcessor.process(XSLTPro
cessor.java:110)
at org.apache.cocoon.Engine.handle(Compiled Code)
at org.apache.cocoon.Cocoon.service(Cocoon.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnectio
n.java:317)
at org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java:479)
--
Rick Tessner rick@myra.com
MYRA Systems Corp. Fone: (250) 381 1335 x125 Phax: (250) 381 1304
Cell: (250) 885 9452
"Hmmm. They have the Internet on computers now!"
RE: Xalan c++ and Windows ATL
Posted by Linda Derezinski <li...@interfacecontrol.com>.
We had a similar problem with integrating XALAN with legacy (Didn't use
namespaces) code. I ended up segregating the XALAN calls into separate
source files. Ended up with friend functions and c-style extern functions.
Linda Derezinski
Interface & Control Systems
-----Original Message-----
From: John Kienitz [mailto:johnk@intertop.com]
Sent: Tuesday, July 18, 2000 6:03 PM
To: xalan-dev@xml.apache.org
Subject: Xalan c++ and Windows ATL
Has anyone attempted to use xalan C++ 0.40 with Windows ATL? We are having
conflicts with the various versions of the iostreams headers when we try to
insert the xalan includes files into an existing project.
Thanks
John Kienitz
Xalan c++ and Windows ATL
Posted by John Kienitz <jo...@intertop.com>.
Has anyone attempted to use xalan C++ 0.40 with Windows ATL? We are having
conflicts with the various versions of the iostreams headers when we try to
insert the xalan includes files into an existing project.
Thanks
John Kienitz