Subject: [xsl] Strange Saxon error From: Stephen Arbour <sarbour@xxxxxxxxx> Date: Wed, 14 Apr 2010 13:29:04 -0400 |
Hi all, We have a customer that was using Saxon 9.1.0.7j using an XSLT transform that was created by a third party. When they upgraded to a version that uses Saxon 9.2.0.2, they started receiving this error: net.sf.saxon.trans.XPathException: Cannot read a document that was written during the same transformation: file:/C:/Program%20Files/K4%20XML%20Exporter/data/xsl/temp/21missouri4.xml However, using the same XSLT in Oxygen 11 using 9.2.0.6 (HE, PE), I can't recreate the error. It only appears when Saxon is called by the application we support. The XSL itself does indeed perform operations on files created by earlier steps in the same XSL. Is this no longer a supported workflow, but somehow Oxygen is intervening where the standalone Saxon jars do not? Thanks in advance for your help! Stephen Arbour, MBA/TM Senior Director of Product Management MEI 610 Old York Road, Suite 250, Jenkintown, PA 19046 Phone: 215-886-5662 x291 Fax: 215-886-5681 Email: sarbour@xxxxxxxxx<mailto:sarbour@xxxxxxxxx> <mailto:LBruce@xxxxxxxxx>AIM: sarbourmei http://www.maned.com<http://www.maned.com/>
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
AW: [xsl] EXSLT replace to XSLT 2.0, Szabo, Patrick \(LNG | Thread | RE: [xsl] Strange Saxon error, Michael Kay |
Re: [xsl] EXSLT replace to XSLT 2.0, Wolfgang Laun | Date | RE: [xsl] Strange Saxon error, Michael Kay |
Month |