Content is not allowed in Prolog SAXParserException

Question

I am trying to call a web service but facing a strange behavior  we have a web-service running on my server but the code is not open to us so can not see what going on behind the wall The owner of the service have exposed  web based test client UI which take input in a text box and will show the response to testing purpose This input box is taking the input in the below mentioned format   lt CONTENT gt    lt CONTENTID gt  lt  CONTENTID gt    lt DOCUMENTID gt DRI2 lt  DOCUMENTID gt    lt LOCALECODE gt en US lt  LOCALECODE gt    lt LATEST VERSION gt false lt  LATEST VERSION gt    lt INCREASEVIEWCOUNT gt false lt  INCREASEVIEWCOUNT gt    lt ACTIVITY TYPE gt  lt  ACTIVITY TYPE gt   lt  CONTENT gt    its working fine on this UI but when i am trying to call this web service through my java code its getting connected as well getting authorized by the service but when i trying to call the above method it giving me the below error message  AxisFault  faultCode   http   schemas xmlsoap org soap envelope  Server userException  faultSubcode    faultString  org xml sax SAXParseException  Content is not allowed in prolog   faultActor    faultNode    faultDetail     http   xml apache org axis  stackTrace 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 org apache xerces jaxp SAXParserImpl JAXPSAXParser parse Unknown Source   at javax xml parsers SAXParser parse SAXParser java 395   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 axis handlers soap MustUnderstandChecker invoke MustUnderstandChecker java 62   at org apache axis client AxisClient invoke AxisClient java 206   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   at com inquira imwows generated ContentServicesSoapBindingStub getContentRecord ContentServicesSoapBindingStub java 262   at com inquira prep GetWebService getcontentRecord GetWebService java 87   at com inquira prep TestWs main TestWs java 13     http   xml apache org axis  hostname umeshawasthi  org xml sax SAXParseException  Content is not allowed in prolog   at org apache axis AxisFault makeFault AxisFault java 101   at org apache axis SOAPPart getAsSOAPEnvelope SOAPPart java 701   at org apache axis Message getSOAPEnvelope Message java 435   at org apache axis handlers soap MustUnderstandChecker invoke MustUnderstandChecker java 62   at org apache axis client AxisClient invoke AxisClient java 206   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   at com inquira imwows generated ContentServicesSoapBindingStub getContentRecord ContentServicesSoapBindingStub java 262   at com inquira prep GetWebService getcontentRecord GetWebService java 87   at com inquira prep TestWs main TestWs java 13  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 org apache xerces jaxp SAXParserImpl JAXPSAXParser parse Unknown Source   at javax xml parsers SAXParser parse SAXParser java 395   at org apache axis encoding DeserializationContext parse DeserializationContext java 227   at org apache axis SOAPPart getAsSOAPEnvelope SOAPPart java 696       11 more   below is the code for generating the required XML  inputXml append   lt CONTENT gt        inputXml append   lt CONTENTID gt    append   lt  CONTENTID gt        inputXml append   lt DOCUMENTID gt    append  DRI2   append   lt  DOCUMENTID gt        inputXml append   lt LOCALECODE gt    append  en US   append   lt  LOCALECODE gt        inputXml append   lt LATEST VERSION gt    append  false   append   lt  LATEST VERSION gt        inputXml append   lt INCREASEVIEWCOUNT gt    append  false   append   lt  INCREASEVIEWCOUNT gt        inputXml append   lt ACTIVITY TYPE gt    append   lt  ACTIVITY TYPE gt        inputXml append   lt  CONTENT gt       and the generated XML is as below   lt CONTENT gt  lt CONTENTID gt  lt  CONTENTID gt  lt DOCUMENTID gt DRI2 lt  DOCUMENTID gt  lt LOCALECODE gt en US lt  LOCALECODE gt  lt LATEST VERSION gt false lt  LATEST VERSION gt  lt INCREASEVIEWCOUNT gt false lt  INCREASEVIEWCOUNT gt  lt ACTIVITY TYPE gt  lt  ACTIVITY TYPE gt  lt  CONTENT gt    i even did timing of the generated string something as below   inputXml toString   trim   replaceFirst       W    lt     lt       but unable to find out whats going wrong one thing i am sure there is some problem in the input XML as its working find on the test Page UI for the same XML  any help in this regard is much appricated

User · Accepted Answer

This error is probably related to a byte order mark (BOM) prior to the actual XML content. You need to parse the returned String and discard the BOM, so SAXParser can process the document correctly.

You will find a possible solution here.

User · Answer

to simply remove it  paste your xml file into notepad  you ll see the extra character before the first tag  Remove it  amp  paste back into your file - bof

User · Answer

This error can come if there is validation error either in your wsdl or xsd file  For instance I too got the same issue while running wsdl2java to convert my wsdl file to generate the client  In one of my xsd it was defined as below   lt xs import schemaLocation    namespace  http   MultiChoice PaymentService DataContracts    gt    Where the schemaLocation was empty  By providing the proper data in schemaLocation resolved my problem    lt xs import schemaLocation  multichoice paymentservice DataContracts xsd  namespace  http   MultiChoice PaymentService DataContracts    gt

User · Answer

Check the XML  It is not a valid xml    Prolog is the first line with xml version info  It ok not to  include it in your xml     This error is thrown when the parser reads an invalid tag at the start of the document  Normally where the prolog resides   e g    Root   lt document gt    Root lt document gt

User · Answer

I faced the same issue  Our application running on four application servers and due to invalid schema location mentioned on one of the web service WSDL  hung threads are generated on the servers   The appliucations got down frequently  After corrected the schema Location   the issue got resolved

[java] Content is not allowed in Prolog SAXParserException

Examples related to java

Examples related to axis2

Examples related to axis

Examples related to webservice-client

Examples related to saxparseexception