More Info: If I edit the sitemap to make Saxon pretend to be Xalan (to ensure that only Saxon is used) then the problem changes. A java source file is generated for the XSP page, but the first line in the file should not be there at all. Here are the first 5 lines from the file hello_xsp.java:
xmlns:xsp="http://apache.org/xsp"; xmlns:XSLTExtension="org.apache.cocoon.components.language.markup.xsp.XSLTExtension" package org.apache.cocoon.www.samples.docs.samples.xsp; import java.io.File; import java.io.IOException; Tim >>> [EMAIL PROTECTED] 12/16/02 10:35AM >>> >I am trying to use Saxon-7.3.1 with Cocoon-2.1 for XSP pages. >It worked until a couple weeks ago (using Saxon-7.3), but broke >around the time that the XSP changes were put in Cocoon-2.1 >for the not-recompiling bug. > >Anybody have ideans or a simillar setup working? > >When I try to access: >http://localhost:8080/cocoon-1216-1/samples/xsp/hello >I get an error that looks like Saxon and Xalan are fighting each other: > >Error: 500 >Location: /cocoon-1216-1/samples/xsp/hello >Internal Servlet Error: > >java.lang.StackOverflowError > at net.sf.saxon.om.NamePool.allocate(NamePool.java:413) > at net.sf.saxon.event.ContentEmitter.getNameCode(ContentEmitter.java:181) > at net.sf.saxon.event.ContentEmitter.startElement(ContentEmitter.java:131) > at org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:130) > at >org.apache.xalan.xsltc.runtime.output.SAXXMLOutput.closeStartTag(SAXXMLOutput.java:312) > at >org.apache.xalan.xsltc.runtime.output.SAXXMLOutput.endElement(SAXXMLOutput.java:205) > at error2html.returns2br() > at error2html.returns2br() > at error2html.returns2br() >(This last line repeats maybe 100 times) > >Tim --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
