| Author |
Message
|
| gpraxi |
 Posted: Tue Jun 17, 2014 7:54 pm Post subject: I am getting malformed xml for "encoding=" in WebS |
 |
|
Newbie
Joined: 17 Jun 2014
Posts: 3
|
| I am getting malformed xml (we are getting extra space in <?xml version="1.0" encoding="UTF-8" ?>)for "encoding=" in WebSphere8 MQ Response. Can anyone help to fix for this, how i can get correct format(Correct Format is :<?xml version="1.0" encoding="UTF-8"?> ). |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Jun 17, 2014 9:30 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
How do you know that the section you quoted is malformed?
What does the XML Spec say about this?
What errors do you see in your flow?
What does the exceptionList look like?
It would help us to help you for you to post more information about your problem at the outset. Examples/Error reports are really good places to start.
If this is truly a malformed message then the normal practice is to go to the sender and get them to correct the problem. IF you do that then quoting the relevant part of the XML Specification would help your argument.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| gpraxi |
| Posted: Tue Jun 17, 2014 10:38 pm Post subject: |
|
|
Newbie
Joined: 17 Jun 2014
Posts: 3
|
thanks, davies
we are sending the message without space <?xml version="1.0" encoding="UTF-8"?> and we are getting the prolog with space as, <?xml version="1.0" encoding="UTF-8" ?> for Queue. I can see in message data we are getting some extra bite N~ for response message. So used MQMD is considering this extra chracter and keeping space inside prolog. I am sharing this comparision in WAS6/WAS8.
Can you please suggest what i am doing wrong |
|
| Back to top |
|
|
| gpraxi |
| Posted: Tue Jun 17, 2014 10:44 pm Post subject: |
|
|
Newbie
Joined: 17 Jun 2014
Posts: 3
|
Comarision for message data for Input/Output Queue:
UTF encoding ( &#nnn; ) is replaced by the 1 byte actual value ( Ñ ) |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 18, 2014 4:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gpraxi wrote: |
Comarision for message data for Input/Output Queue:
UTF encoding ( &#nnn; ) is replaced by the 1 byte actual value ( Ñ ) |
As as my worthy associate says, go back to whoever's generating the response and get them to fix it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
