on 12-03-2007 9:04 PM
The source XML file includes above field. When I tried to test the message mapping using the source xml file with the above tag.Message mapping resulted in an error "XML is not well formed". Does any body have any idea how to prevent this in XI ?
Hello kamath,
Thanks for the immediate response.
I tried the encoding option you provided, it resulted in the same error. But I used a similar one "iso-8859-1" with iso prefixed and Message mapping test is successful.
Your answer was helpful.
Thanks,
Nivedita
Highly appreciate all of your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response.
<?xml version="1.0" encoding="UTF-8" ?>
I have the encoding option at the top of the xml file but still get the error "XML file not well formed".
Does this need to be fixed in XI or java ? If this needs to be fixed in XI then how ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<LOCATION>México_DF_MX</LOCATION>
It has nothing to do with above filed. Ther must be some thing else wrong with in the mapping. The above tag successfully executed in one of my mappings.. check if all the tags are properly closed in the source xml.
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello VJ,
The error "XML not well formed" is due to the accent words in the field value in the source XML file. But when we remove the accent mark the MM test is successful.
How do I prevent this accent mark in xml file ? Should we take of this in XI or Java code ?
Highly appreciate your help.
Thanks,
Nivedita
Hello Nivedita,
I had a similar requirement couple of years ago and not much has changed in how we can handle xml containing unwanted special characters. I ended up creating a java bean (ejb) which removed the special character and replaced it with space. Writing a ejb can pose its own challenges but this is a sure way to fix the problem. I used NWDS to code and deployed it as a service to XI engine.
Let me know if you need any documentation on this...there are plenty of advices and links pdf floating around in SDN.
Thanks,
Pam
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.