Question
Veteran Careers First
US
Last activity: 26 May 2019 11:38 EDT
XML with BOM
We currently processing XML files from directory.
Listener picks up files to parse and send to DB.
Some of the files failed with the following error.
**Failed to parse XML. Error: Content is not allowed in prolog.
The reason appears to be that these files have (BOM) Bytes Order Marker at the beginning.
How can PEGA identify and remove BOM so the incoming XML files can still process.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
What Pega version are you using?
Veteran Careers First
US
7.2
Veteran Careers First
US
7.2.2
Pegasystems Inc.
FR
Hello,
I haven't seen this issue on Pega 7.2.2. How did you come to the conclusion that it was because of BOM characters?
Veteran Careers First
US
We used a hex editor/viewer to look at the data.
For ex. command Linux command hexdump.
But there are other hex editors available.
Lantiqx
GB
Hi Marc,
We have seen similar issue in 7.3.1, any pointers to HotFix(if any) or work around will be much appreciated.
Thanks in Advance.
-
Mandeep Rawat Phil Shannon Pavankumar A S
Standard Chartered Global Business Services Sdn. Bhd.
MY
Any work around / suggestions welcome. similar issue we are facing in the pega722.
If i try the same xml file in notepad++ and change the encoding to utf-8 its working
-The file heading starts like this <?xml version="1.0" encoding="utf-8"?> when i read by notepad++ its showing the xml as utf-8 bom.
Pegasystems Inc.
IN
Publicis Sapient
IN
Hi,
You can try selecting the character encoding as "UTF-8" in the method tab of Service File to remove the Byte Order Mark from the Input file