org.xml.sax.SAXParseException: Content is not allowed in prolog

2004-11-05 Thread John McCosker
Title: org.xml.sax.SAXParseException: Content is not allowed in prolog hi, I am connecting to an axis web service fine, but within it a class is parsing a local xml file using xerces / sax, tomcat has logged the SAXParseException and the reason is "Content is not allowed in prolog&

Re: "Content is not allowed in prolog" exception

2004-07-01 Thread NJ Rogers, Learning and Research Technology
i I get a SAX parser exception as "Content is not allowed in prolog" while parsing the response. I have included the response that I receive from the server and the stack trace of the exception. Also there are no junk characters before or after the response. Can someone please explain what can cau

"Content is not allowed in prolog" exception

2004-06-30 Thread Ramya Manian
Hi I get a SAX parser exception as "Content is not allowed in prolog" while parsing the response. I have included the response that I receive from the server and the stack trace of the exception. Also there are no junk characters before or after the response. Can someone please explai

Content is not allowed in prolog

2004-04-20 Thread Scott Hopkins
am using Axis in combination with Xerces to connect to a .Net web service. I get a response correctly but Xerces throws a "Content is not allowed in prolog" exception when parsing. I believe this is because there is a Byte Order Mark (BOM) in the response (the ? showing up right before

Content is not allowed in prolog.

2003-11-19 Thread gbartha
utl_http.read_text(http_resp, env); utl_http.end_response(http_resp); ... If I don't know myt message's size I have to use the 'Transfer-Encoding', 'chunked' header. In this case I get the following error from the Axis: soapenv:Server.userException org.xml.sax.