Hi Raoul,
quick answer without knowing the changes ... :-(
+) if you are accessing your XSL using filesystem related functionality
then the includes are resolved relative to your XSL.
+) if you are just getting an input stream the XSLT processor has no
idea where your XSL resides and tries probable the current working
directory.
cheers,
Siegfried Goeschl
rc wrote:
Hi all,
I'm upgrading from turbine 2.3.1 to 2.3.2, because I saw a change
with forwarding parameters throw XSL transformations.
But I can't transform anymore due to a FileNotFoundException with
files included inside base xsl files (xsl:include href="tools.xsl");
So, base xsl file is found, but included ones not:
java.io.FileNotFoundException:
/path-to-catalina-start-directory/tools.xsl (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
at java.net.URL.openStream(URL.java:913)
at
org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at
org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:305)
at
org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclude.java:184)
at
org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:636)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at
org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:892)
at
org.apache.turbine.services.xslt.TurbineXSLTService.compileTemplates(TurbineXSLTService.java:149)
at
org.apache.turbine.services.xslt.TurbineXSLTService.getTemplates(TurbineXSLTService.java:180)
at
org.apache.turbine.services.xslt.TurbineXSLTService.transform(TurbineXSLTService.java:205)
at
org.apache.turbine.services.xslt.TurbineXSLTService.transform(TurbineXSLTService.java:233)
at
org.apache.turbine.services.xslt.TurbineXSLT.transform(TurbineXSLT.java:50)
So my question is: is the URL accessing method throw servlet container
making trouble with
xsl:include node, or did i do something wrong ?
Regards,
Raoul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
