Wrong format of XML

[d_chandrasekhar]

Hi all,

I have a peculiar problem. There is a file in unix. But when the XI polls the file , it goes as error. When I check the payload , one of the element has end tag missing.

e.g : <field1>

&@^#&*@# /field1>.

The file in the unix path is correct. What can be the possible problem?

The field contains non-english characters.

Thanks in advance

Sekhar

[d_chandrasekhar]

Hi,

The file in the unix has no probems. The tags are all correct. Infact if I download the unix file as a local file , the XML is well formed. Problem start when the XI picks it up. And the field has chinese characters and not special chars.I dont know if I am missing anything.

Thanks and Regards

Sekhar

[Former Member]

But what you post in your question that was special characters

Did you checked message in CC monitoring? What payload you are seeing in Sedner File Adapter (in CCM)?

Also as far as Chiness char are concern then XI support it.

Also as Stefan said, plz check the XML message header.

Thanks

Farooq

[Former Member]

>>Infact if I download the unix file as a local file , the XML is well formed.

Then did u tried to send this XML message to IE engine using RWB- Message Test Tool? Did it sent message without any error to IE? Is the payload is visible in IE that u sent from RWB?

Thanks

Farooq

[stefan_grube]

I think the codepage of the XML file is not UTF-8.

Check the charset declaration in the XML header.

Check also the file adapter channel parameters.

Regards

Stefan

[Former Member]

>><field1>&@^#&*@# /field1>.

your payload contians special character that is not supported in XI.

Refer this Blog for more details : [Handling the Special Characters in XI|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420] [original link is broken] [original link is broken] [original link is broken];

Thanks

Farooq

Edited by: Farooq Farooqui on Sep 6, 2008 9:10 PM

[Former Member]

Check whether all the tags are closed .

<Header>

</Header>.

<XXXXXXX>

</XXXXXXX>.

If the end tag is not there then you may get this problem.

Copy the payload try to run a test in message mapping the test result will help you to narrow down the error point.