Hi Neil, I've attached the document in question as a zipped attachment.
I've played around with this further and have found no problems parsing the document using the sample SAX-based examples included with the Xerces 2.2.1 distribution. I'm starting to wonder if it could be related to how the JSP engine sets up its parser, but I'm not sure what that would be at this point in time. So, I'm not sure if the help I need is going to be found here now :) Thanks, -rl On Mon, 2002-11-25 at 16:10, [EMAIL PROTECTED] wrote: > Hi Ryan, > > It'll definitely be necessary to see the document that's giving you > problems. Sending it as a zipped attachment would be preferred, since that > way we'll know we're getting the original you're testing with. > > Thanks, > Neil > Neil Graham > XML Parser Development > IBM Toronto Lab > Phone: 905-413-3519, T/L 969-3519 > E-mail: [EMAIL PROTECTED] > > > > > |---------+----------------------------> > | | Ryan Lubke | > | | <[EMAIL PROTECTED]| > | | OM> | > | | | > | | 11/25/2002 03:49 | > | | PM | > | | Please respond to| > | | xerces-j-user | > | | | > |---------+----------------------------> > > >---------------------------------------------------------------------------------------------------------------------------------------------| > | > | > | To: [EMAIL PROTECTED] > | > | cc: > | > | Subject: "Content not allowed in prolog" returned when attempting > to parse document encoded in UTF-16 | > | > | > | > | > > >---------------------------------------------------------------------------------------------------------------------------------------------| > > > > Hello, > > Xerces version: Xerces for J2 (nightly build) > > I'm trying use a JSP in "XML Syntaxt" with the latest Tomcat 5.0. > The JSP Document in question is encoded in UTF-16. I've double checked > that the encoded document does have the BOM so autodetection by the > parser should occur: > > od -x Test.jspx > 0000000 fffe 3c00 3f00 7800 6d00 6c00 2000 7600 > > So based on the XML specification, this is UTF-16, little endian. > > When I try to load the JSP in Tomcat, I receive the following: > > -------------------------------------------------- > org.apache.jasper.JasperException: null(1,1) Content is not allowed in > prolog. > at > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94) > > at > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:444) > > at > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:242) > > . > . > org.xml.sax.SAXParseException: Content is not allowed in prolog. > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > at javax.xml.parsers.SAXParser.parse(Unknown Source) > at > org.apache.jasper.compiler.JspDocumentParser.parse(JspDocumentParser.java:180) > > at > org.apache.jasper.compiler.ParserController.parseFile(ParserController.java:204) > > -------------------------------------------------- > > I've verified also that there is no whitespace preceding or trailing the > prolog. > I've check various bug databases with no luck, and search for similar > issues on Google > haven't yielded anything useful. > > I'm hoping someone out here has an idea. > > Thanks, > > -rl > > PS. Please CC me in the reply as I just subscribed to this user list and > I'm not sure > how long it takes to go into effect. > > > > --------------------------------------------------------------------- > 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] -- Ryan Lubke <[EMAIL PROTECTED]> Sun Microsystems, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
