org xml sax SAXParseException Content is not allowed in prolog

Question

I have a Java based web service client connected to Java web service  implemented on the Axis1 framework     I am getting following exception in my log file   Caused by  org xml sax SAXParseException  Content is not allowed in prolog      at org apache xerces util ErrorHandlerWrapper createSAXParseException Unknown Source      at org apache xerces util ErrorHandlerWrapper fatalError Unknown Source      at org apache xerces impl XMLErrorReporter reportError Unknown Source      at org apache xerces impl XMLErrorReporter reportError Unknown Source      at org apache xerces impl XMLScanner reportFatalError Unknown Source      at org apache xerces impl XMLDocumentScannerImpl PrologDispatcher 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 XML11Configuration parse Unknown Source      at org apache xerces parsers XMLParser parse Unknown Source      at org apache xerces parsers AbstractSAXParser parse Unknown Source      at javax xml parsers SAXParser parse Unknown Source      at org apache axis encoding DeserializationContext parse DeserializationContext java 227      at org apache axis SOAPPart getAsSOAPEnvelope SOAPPart java 696      at org apache axis Message getSOAPEnvelope Message java 435      at org apache ws axis security WSDoAllReceiver invoke WSDoAllReceiver java 114      at org apache axis strategies InvocationStrategy visit InvocationStrategy java 32      at org apache axis SimpleChain doVisiting SimpleChain java 118      at org apache axis SimpleChain invoke SimpleChain java 83      at org apache axis client AxisClient invoke AxisClient java 198      at org apache axis client Call invokeEngine Call java 2784      at org apache axis client Call invoke Call java 2767      at org apache axis client Call invoke Call java 2443      at org apache axis client Call invoke Call java 2366      at org apache axis client Call invoke Call java 1812

User · Answer

I took code of Dineshkumar and modified to Validate my XML file correctly:

_x000D_

import org.apache.log4j.Logger;_x000D_
_x000D_
public class Myclass{_x000D_
_x000D_
private static final Logger LOGGER = Logger.getLogger(Myclass.class);_x000D_
_x000D_
/**_x000D_
 * Validate XML file against Schemas XSD in pathEsquema directory_x000D_
 * @param pathEsquema directory that contains XSD Schemas to validate_x000D_
 * @param pathFileXML XML file to validate_x000D_
 * @throws BusinessException if it throws any Exception_x000D_
 */_x000D_
public static void validarXML(String pathEsquema, String pathFileXML) _x000D_
 throws BusinessException{ _x000D_
 String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";_x000D_
 String nameFileXSD = "file.xsd";_x000D_
 String MY_SCHEMA1 = pathEsquema+nameFileXSD);_x000D_
 ParserErrorHandler parserErrorHandler;_x000D_
 try{_x000D_
  SchemaFactory schemaFactory = SchemaFactory.newInstance(W3C_XML_SCHEMA);_x000D_
  _x000D_
  Source [] source = { _x000D_
   new StreamSource(new File(MY_SCHEMA1))_x000D_
   };_x000D_
  Schema schemaGrammar = schemaFactory.newSchema(source);_x000D_
_x000D_
  Validator schemaValidator = schemaGrammar.newValidator();_x000D_
  schemaValidator.setErrorHandler(_x000D_
   parserErrorHandler= new ParserErrorHandler());_x000D_
  _x000D_
  /** validate xml instance against the grammar. */_x000D_
  File file = new File(pathFileXML);_x000D_
  InputStream isS= new FileInputStream(file);_x000D_
  Reader reader = new InputStreamReader(isS,"UTF-8");_x000D_
  schemaValidator.validate(new StreamSource(reader));_x000D_
  _x000D_
  if(parserErrorHandler.getErrorHandler().isEmpty()&& _x000D_
   parserErrorHandler.getFatalErrorHandler().isEmpty()){_x000D_
   if(!parserErrorHandler.getWarningHandler().isEmpty()){_x000D_
    LOGGER.info(_x000D_
    String.format("WARNING validate XML:[%s] Descripcion:[%s]",_x000D_
     pathFileXML,parserErrorHandler.getWarningHandler()));_x000D_
   }else{_x000D_
    LOGGER.info(_x000D_
    String.format("OK validate  XML:[%s]",_x000D_
     pathFileXML));_x000D_
   }_x000D_
  }else{_x000D_
   throw new BusinessException(_x000D_
    String.format("Error validate  XML:[%s], FatalError:[%s], Error:[%s]",_x000D_
    pathFileXML,_x000D_
    parserErrorHandler.getFatalErrorHandler(),_x000D_
    parserErrorHandler.getErrorHandler()));_x000D_
  }  _x000D_
 }_x000D_
 catch(SAXParseException e){_x000D_
  throw new BusinessException(String.format("Error validate XML:[%s], SAXParseException:[%s]",_x000D_
   pathFileXML,e.getMessage()),e);_x000D_
 }_x000D_
 catch (SAXException e){_x000D_
  throw new BusinessException(String.format("Error validate XML:[%s], SAXException:[%s]",_x000D_
   pathFileXML,e.getMessage()),e);_x000D_
 }_x000D_
 catch (IOException e) {_x000D_
  throw new BusinessException(String.format("Error validate XML:[%s], _x000D_
   IOException:[%s]",pathFileXML,e.getMessage()),e);_x000D_
 }_x000D_
 _x000D_
}_x000D_
_x000D_
}

_x000D_

User · Answer

Set your document to form like this    lt  xml version  1 0  encoding  UTF-8    gt   lt root gt       children   lt  root gt

User · Answer

I had the same issue with spring      MarshallingMessageConverter   and by pre-proccess code   Mayby someone will need reason  BytesMessage  readBytes - reading bytes   and i forgot that reading is one direction operation  You can not read twice

User · Answer

I had the same issue   First I downloaded the XML file to local desktop and I got Content is not allowed in prolog during the importing file to portal server  Even visually file was looking good to me but somehow it s was corrupted    So I re-download the same file and tried the same and it worked

User · Answer

Actually in addition to Yuriy Zubarev s Post  When you pass a nonexistent xml file to parser  For example you pass   new File  C  temp abc     when only C  temp abc xml file exists on your file system  In either case  builder   DocumentBuilderFactory newInstance   newDocumentBuilder    document   builder parse new File  C  temp abc       or  DOMParser parser   new DOMParser    parser parse  file C  temp abc      All give the same error message   Very disappointing bug  because the following trace  javax servlet ServletException     at org apache xerces parsers DOMParser parse Unknown Source      Caused by  org xml sax SAXParseException  Content is not allowed in prolog      40 more   doesn t say anything about the fact of  file name is incorrect  or  such a file does not exist   In my case I had absolutely correct xml file and had to spent 2 days to determine the real problem

User · Answer

In my case  removing the  encoding  UTF-8   attribute altogether worked   It looks like a character set encoding issue  maybe because your file isn t really in UTF-8

User · Answer

This is often caused by a white space before the XML declaration  but it could be any text  like a dash or any character  I say often caused by white space because people assume white space is always ignorable  but that s not the case here     Another thing that often happens is a UTF-8 BOM  byte order mark   which is allowed before the XML declaration can be treated as whitespace if the document is handed as a stream of characters to an XML parser rather than as a stream of bytes   The same can happen if schema files   xsd  are used to validate the xml file and one of the schema files has an UTF-8 BOM

User · Answer

I had the same problem  and solved it  while trying to parse an XML document with freemarker   I had no spaces before the header of XML file   The problem occurs when and only when the file encoding and the XML encoding attribute are different   ex  UTF-8 file with UTF-16 attribute in header    So I had two ways of solving the problem    changing the encoding of the file itself changing the header UTF-16 to UTF-8

User · Answer

We had the same problem recently and it turned out to be the case of a bad URL and consequently a standard 403 HTTP response  which obviously isn t the valid XML the client was looking for   I m going to share the detail in case someone within the same context run into this problem   This was a Spring based web application in which a  JaxWsPortProxyFactoryBean  bean was configured to expose a proxy for a remote port    lt bean id  ourPortJaxProxyService      class  org springframework remoting jaxws JaxWsPortProxyFactoryBean      p serviceInterface  com amir OurServiceSoapPortWs      p wsdlDocumentUrl    END POINT BASE URL  OurService wsdl      p namespaceUri  http   amir com jaxws  p serviceName  OurService      p portName  OurSoapPort    gt    The  END POINT BASE URL  is an environment variable configured in  setenv sh  of the Tomcat instance that hosts the web application  The content of the file is something like this   export END POINT BASE URL  http   localhost 9001 BusinessAppServices   export END POINT BASE URL  http   localhost 8765 BusinessAppServices    The missing     after each line caused the malformed URL and thus the bad response  That is  instead of  BusinessAppServices OurService wsdl  the URL had a CR before       TCP IP Monitor  was quite handy while troubleshooting the problem

User · Answer

As Mike Sokolov has already pointed it out  one of the possible reasons is presence of some character s  such as a whitespace  before the  tag   If your input XML is being read as a String  as opposed to byte array  then you can use replace your input string with the below code to make sure that all  un-necessary  characters before the xml tag are wiped off   inputXML inputXML substring inputXML indexOf   lt  xml       You need to be sure that the input xml starts with the xml tag though

User · Answer

For me  a Build- Clean fixed everything

User · Answer

It means XML is malformed or the response body is not XML document at all

User · Answer

If all else fails  open the file in binary to make sure there are no funny characters  3 non printable characters at the beginning of the file that identify the file as utf-8  at the beginning of the file  We did this and found some  so we converted the file from utf-8 to ascii and it worked

User · Answer

In my case I got this error because the API I used could return the data either in XML or in JSON format  When I tested it using a browser  it defaulted to the XML format  but when I invoked the same call from a Java application  the API returned the JSON formatted response  that naturally triggered a parsing error

User · Answer

Just spent 4 hours tracking down a similar problem in a WSDL   Turns out the WSDL used an XSD which imports another namespace XSD   This imported XSD contained the following    lt  xml version  1 0  encoding  UTF-8   gt   lt schema targetNamespace  http   www xyz com Services CommonTypes  elementFormDefault  qualified      xmlns  http   www w3 org 2001 XMLSchema       xmlns xsd  http   www w3 org 2001 XMLSchema      xmlns CommonTypes  http   www xyz com Services CommonTypes  gt     lt include schemaLocation    gt  lt  include gt         lt complexType name  RequestType  gt           lt        Note the empty include element   This was the root of my woes   I guess this is a variation on Egor s file not found problem above      1 to disappointing error reporting

User · Answer

I followed the instructions found here and i got the same error   I tried several things to solve it  ie changing the encoding  typing the XML file rather than copy-pasting it ect  in Notepad and XML Notepad but nothing worked   The problem got solved when I  edited and saved my XML file in Notepad    encoding --  utf-8 without BOM

User · Answer

Try with BOMInputStream in apache commons io   public static  lt T gt  T getContent Class lt T gt  instance  SchemaType schemaType  InputStream stream  throws JAXBException  SAXException  IOException        JAXBContext context   JAXBContext newInstance instance       Unmarshaller unmarshaller   context createUnmarshaller        Reader reader   new InputStreamReader new BOMInputStream stream    UTF-8         JAXBElement lt T gt  entry   unmarshaller unmarshal new StreamSource reader   instance        return entry getValue

User · Answer

What i have tried  Did not work  In my case the web xml in my application had extra space  Even after i deleted   it did not work   I was playing with logging properties and web xml in my tomcat  but even after i reverted the error persists   Solution To be specific i tried do adding org apache catalina filters ExpiresFilter level   FINE Tomcat expire filter is not working correctly

User · Answer

I encountered similar problem with jenkins junit report plugin  It turns out you have to specify   xml  even if you create junit xml in home directory   So Test report XMLs   xml    or targeted directory  xml

User · Answer

Just an additional thought on this one for the future   Getting this bug could be the case that one simply hits the delete key or some other key randomly when they have an XML window as the active display and are not paying attention   This has happened to me before with the struts xml file in my web application   Clumsy elbows

User · Answer

To fix the BOM issue on Unix   Linux systems    Check if there s an unwanted BOM character  hexdump -C myfile xml   more An unwanted BOM character will appear at the start of the file as     lt  xml gt  Alternatively  do file myfile xml  A file with a BOM character will appear as  myfile xml  XML 1 0 document text  UTF-8 Unicode  with BOM  text Fix a single file with  tail -c  4 myfile xml  gt  temp xml  amp  amp  mv temp xml myfile xml Repeat 1 or 2 to check the file has been sanitised  Probably also sensible to do view myfile xml to check contents have stayed     Here s a bash script to sanitise a whole folder of XML files      usr bin env bash    This script is to sanitise XML files to remove any BOM characters  has bom     head -c3   1    LC ALL C grep -qe   xef xbb xbf      for filename in   xml   do   if has bom   filename   then     tail -c  4   filename   gt  temp xml     mv temp xml   filename    fi done

User · Answer

Try adding a space between the encoding  UTF-8  string in the prolog and the terminating   gt    In XML the prolog designates this bracket-question mark delimited element at the start of the document  while the tag prolog in stackoverflow refers to the programming language    Added  Is that dash in front of your prolog part of the document   That would be the error there  having data in front of the prolog  - lt  xml version  1 0  encoding  UTF-8   gt

User · Answer

For the same issues  I have removed the following line     File file   new File  c   file xml      InputStream inputStream  new FileInputStream file     Reader reader   new InputStreamReader inputStream  UTF-8      InputSource is   new InputSource reader     is setEncoding  UTF-8      It is working fine  Not so sure why that UTF-8 gives problem  To keep me in shock  it works fine for UTF-8 also   Am using Windows-7 32 bit and Netbeans IDE with Java  jdk1 6 0 13   No idea how it works

User · Answer

I had the same problem with some XML files  I solved reading the file with ANSI encoding  Windows-1252  and writing a file with UTF-8 encoding with a small script in Python  I tried use Notepad   but I didn t have success   import os import sys  path   os path dirname   file     file name    my input file xml   if   name         main         with open os path join path         file name    r   encoding  cp1252   as f1          lines   f1 read           f2   open os path join path          my output file xml     w   encoding  utf-8           f2 write lines          f2 close

User · Answer

First clean project  then rebuild project  I was also facing the same issue  Everything came alright after this

User · Answer

Even I had faced a similar problem  Reason was some garbage character at the beginning of the file    Fix   Just open the file in a text editor tested on Sublime text  remove any indent if any in the file and copy paste all the content of the file in a new file and save it  Thats it   When I ran the new file it ran without any parsing errors

User · Answer

I was having the same problem while parsing the info plist file in my mac  However  the problem was fixed using the following command which turned the file into an XML    plutil -convert xml1 info plist   Hope that helps someone

User · Answer

My answer wouldn t help you probably  but it help with this problem generally    When you see this kind of exception you should try to open your xml file in any Hex Editor and sometime you can see additional bytes at the beginning of the file which text-editor doesn t show    Delete them and your xml will be parsed

User · Answer

Sometimes it s the code  not the XML  The following code   Document doc   dBuilder parse new InputSource new StringReader  file xml        will also result in this error       Fatal Error   1 1  Content is not allowed in prolog org xml sax SAXParseException  lineNumber  1  columnNumber  1  Content is not allowed in prolog    because it s attempting to parse the string literal   file xml   not the contents of the file xml file  and failing because  file xml  as a string is not well-formed XML   Fix  Remove StringReader     Document doc   dBuilder parse new InputSource  file xml       Similarly  dirty buffer problems can leave residual junk ahead of the actual XML   If you ve carefully checked your XML and are still getting this error  log the exact contents being passed to the parser  sometimes what s actually being  tried to be  parsed is surprising

User · Answer

For all those that get this error  WARNING  Catalina start using conf server xml  Content is not allowed in prolog   Not very informative   but what this actually means is that there is garbage in your conf server xml file   I have seen this exact error in other XML files   this error can be caused by making changes with a text editor which introduces the garbage   The way you can verify whether or not you have garbage in the file is to open it with a  HEX Editor  If you see any character before this string         lt  xml version  1 0  encoding  UTF-8   gt     like this would be garbage                lt  xml version  1 0  encoding  UTF-8   gt     that is your problem     The Solution is to use a good HEX Editor   One that will allow you to save files with differing types of encoding     Then just save it as UTF-8  Some systems that use XML files may need it saved as UTF NO BOM  Which means with  NO Byte Order Mark   Hope this helps someone out there

User · Answer

I was also getting the same   XML reader error  javax xml stream XMLStreamException  ParseError at  row col   1 2  Message  Reference is not allowed in prolog      when my application was creating a XML response for a RestFull Webservice call         While creating the XML format String I replaced the  amp lt and  amp gt with  lt  and   then the error went off  and I was getting proper response  Not sure how it worked but it worked   sample   String body     lt ns addNumbersResponse xmlns ns   http   java duke org   gt  lt ns return gt                sum                lt  ns return gt  lt  ns addNumbersResponse gt

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

Examples related to java

Examples related to xml