| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [Solved]UPES, XML and non-ascii characters |
« View previous topic :: View next topic » |
| Author |
Message
|
| TJW |
 Posted: Thu Jun 19, 2003 1:35 am Post subject: [Solved]UPES, XML and non-ascii characters |
 |
|
Novice
Joined: 11 Dec 2002
Posts: 16
Location: UK
|
Has anyone had any success in using non-ascii characters in a UPES XML message?
As part of the return message for a synchronous activity I am trying to send a string which contains an e-acute character. Workflow keeps rejecting the message with an Interface Error.
(MQWF v3.3.2 SP2 on NT - if that helps)
Thanks in advance for any help.
Last edited by TJW on Fri Jun 20, 2003 1:40 am; edited 1 time in total |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Jun 19, 2003 5:35 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
TJW:
I don't have experience with exactly what you are doing, but I can tell you that I encode "unliked" characters like the & using the scheme &#nnn where nnn is the value of the character. This gives me & for the & character.
Let us know if this works for you.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kriersd |
| Posted: Thu Jun 19, 2003 7:30 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
TJW
I would highly recommend you use a parser to create the XML document that gets sent back to the Workflow server. This way the parser will encode those types of characters for you.
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| TJW |
| Posted: Fri Jun 20, 2003 1:37 am Post subject: |
|
|
Novice
Joined: 11 Dec 2002
Posts: 16
Location: UK
|
Dave, John
Thanks for your input. Unfortunately the application generating the messages is pretty inflexible, so it would not be very easy to run the data through an XML parser or encoder.
I tracked down the problem to the header - <?xml version="1.0" standalone="yes"?> - in the messages being generated. The lack of an encoding attribue means a default encoding of UTF-8 is used, and as the characters being sent are not encoded in this format the message is rejected by workflow.
By configuring the application to write a correct header - <?xml encoding="ISO-88591" ...> - I have been able to get workfow to accept the messages. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
