[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XSLT 2.0 compability issue occured in topicmerge.X
>[xslt]
D:\InfoShare\DataSOMC\PublishingService\Data\DataExports\GUID-AA6DE3A2-8ECD-47B5-9839-4C705E444AC4.20120618182735036\1\en\out\GUID-F6C2D026-C2A6-4376-AD33-EB2BF5AE0544.psmi:1:39:
Fatal Error! Error reported by XML parser Cause:
org.xml.sax.SAXParseException: Content is not allowed in prolog.
>It looks like a Saxon issue. Lots of people tend to assume that, despite the fact that Saxon was very careful to say that the error comes from the XML parser (which is not part of Saxon), and the XML parser is explicit that the problem is with the data it is being asked to process. "Content not allowed in prolog" is a message that comes from Xerces and can mean a great number of things. It basically means that it succeeded in opening an input stream, but what it found there wasn't an XML document. The "1:39" is a line and column number, and the fact that 39 is roughly the length of a typical XML declaration might well be suggestive. Perhaps the file contains an XML declaration and nothing else. Michael Kay Saxonica
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|