Answer by Thomas Visel for Fatal Error :1:1: Content is not allowed in prolog
I wanted YAML for the log4j2 configuration file because it doffs XML's visual clutter, but had the same error as Guest96. I scoured the web for a solution to the above, investigating a Utf-8 BOM or...
View ArticleAnswer by Mike for Fatal Error :1:1: Content is not allowed in prolog
It could be not supported file encoding. Change it to UTF-8 for example.I've done this using Sublime
View ArticleAnswer by Sastry for Fatal Error :1:1: Content is not allowed in prolog
The real solution that I found for this issue was by disabling any XML Format post processors. I have added a post processor called "jp@gc - XML Format Post Processor" and started noticing the error...
View ArticleAnswer by Daniel Nelson for Fatal Error :1:1: Content is not allowed in prolog
Looks like you forgot adding correct headers to your get request (ask the REST API developer or you specific API description):HttpURLConnection connection =...
View ArticleAnswer by smiron for Fatal Error :1:1: Content is not allowed in prolog
Someone should mark Johannes Weiß's comment as the answer to this question. That is exactly why xml documents can't just be loaded in a DOM Document class.http://en.wikipedia.org/wiki/Byte_order_mark
View ArticleAnswer by MvG for Fatal Error :1:1: Content is not allowed in prolog
I'm turning my comment to an answer, so it can be accepted and this question no longer remains unanswered.The most likely cause of this is a malformed response, which includes characters before the...
View ArticleAnswer by Johannes Weiss for Fatal Error :1:1: Content is not allowed in prolog
There are certainly some weird characters (e.g. BOM) or some whitespace before the XML preamble (<?xml ...?>)?
View ArticleFatal Error :1:1: Content is not allowed in prolog
I'm using Java and i'm trying to get XML document from some http link. Code I'm using is:URL url = new URL(link);HttpURLConnection connection =...
View Article