Fetch WSDL Error: Unexpected first character (char code 0xEF), not valid in xml document: could be mangled UTF-8 BOM marker. Make

[abiramradhakris]

Hi,

One of my wsdl when referenced with URL (for SOAP Proxy creation with URL reference to WSDL)

https://my.xxx.com/vx/JUMP_START/soap?wsdl

Once validated gives following error.

Fetch WSDL Error: Unexpected first character (char code 0xEF), not valid in xml document: could be mangled UTF-8 BOM marker. Make sure that the Reader uses correct encoding or pass an InputStream instead

As another option I downloaded the WSDL and tried referring the WSDL file locally in windows gives following error..

Fetch WSDL Error: There was an error processing the WSDL

When I open it in browser or in wordpad it shows up fine.

[DChiesa]

You may have to strip the partial or broken BOM from the WSDL.

Wordpad may be making some guesses that other systems don't make.

[isaias_arellano]

Some xmls get messed up for some parsers depending on what tools was used to generated or system did generated it, you can find the answer here, it helped me before

https://stackoverflow.com/questions/34783452/cannot-parse-xml-error-non-whitespace-before-first-tag-...

Basically get rid of any characters before the tag start <

[isaias_arellano]

By character I meant anything an specially control hidden characters