| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with Spain Char |
« View previous topic :: View next topic » |
| Author |
Message
|
| SANTYP |
 Posted: Wed Jun 09, 2010 12:33 am Post subject: Issue with Spain Char |
 |
|
Centurion
Joined: 27 Mar 2007
Posts: 142
|
Hi All, I have an issue with spain character
I do describe about my flow here.
Gateway flow :
soap input node --> operation flow(sublfow) --> soap reply node
Operation flow:
httpinput -- compute --> httpreply
this is my flow in brief.
So in one of the operation flow I am updating a customer address details with spain char (I send a request using soapUI).
till now it is fine. its updated successfully.
but while retrieving the same customer address details, i am getting an unicode exception.
messsage is not able to parse the spain char
it is failing in operation flow before httpreply node.
plz help me out to resolve the issue.
Here is the exception details.
com.barclays.bem.individualcustomermanagement.IndividualCustomerManagement_ResponseTypeValidation.Main :: 5.23 :: 3 :: 1504 :: 2 :: 1 :: 1 :: An invalid XML character (Unicode: 0xffffffff) was found in the prolog of the document. :: /Root/XMLNSC |
|
| Back to top |
|
 |
| AndreasMartens |
| Posted: Wed Jun 09, 2010 1:43 am Post subject: info_needed |
|
|
Acolyte
Joined: 30 Jan 2006
Posts: 65
Location: Hursley, UK
|
Hi Santyp,
Could you tell us:
1. the CCSID / codepage that's set in the XML of the message from SoapUI
2. the CCSID / codepage that's set in the XML of the message between the flows.
To get this, wire in a trace node right after your SOAP Input node and one right after your HTTP Input node with the following it:
${Root}
(and choose to trace to a file..)
This will tell you everything about the message, including Properties.CodedCharSetId.
What I'm trying to get at is that the CCSID that you're sending the message under may not be capable of holding the Spanish character...
The second possibility is that the place you're storing the data is incapable of holding the Spanish character. I'm assuming it's a database, have you checked your database definition to see the codepage it's using?
If neither of these checks tell us anything, the next step will be to user-trace it. I'm a little worried that it's complaining about a character in the prolog of the document... The prolog of the document should always be in the CCSID that the HTTP headers defined, and if they didn't define anything I believe it should be in Latin-1.
The exception seems to be coming from a Java class, are you using a JavaCompute to process your message? You're not using getBytes() on a filestream are you?
cheers,
Andreas |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 09, 2010 3:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
If the CCSID is wrong, the XMLNSC parser almost always reports an error while parsing the prolog ( because the prolog is the first thing that it encounters in the message ).
I agree with AndreasMartens - check that the CCSID is set correctly. Take a user trace if you don't find the problem straight away. |
|
| Back to top |
|
|
| SANTYP |
| Posted: Thu Jun 10, 2010 10:43 pm Post subject: |
|
|
Centurion
Joined: 27 Mar 2007
Posts: 142
|
| kimbert wrote: |
If the CCSID is wrong, the XMLNSC parser almost always reports an error while parsing the prolog ( because the prolog is the first thing that it encounters in the message ).
I agree with AndreasMartens - check that the CCSID is set correctly. Take a user trace if you don't find the problem straight away. |
Yes you guys are correct, its a problem with CCSID,
http request node not able to arparse the message xmlnsc message when it contains spain characters.
I used blob parse instead and in the next compute node I used
below statement to create the logical tree structure.
CREATE LASTCHILD OF OutputRoot DOMAIN('XMLNSC') PARSE(InputRoot.BLOB.BLOB ENCODING 0 CCSID 0);
which now contains the spain characters. |
|
| Back to top |
|
|
| paranoid221 |
| Posted: Sun Jun 13, 2010 10:49 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 101
Location: USA
|
| SANTYP wrote: |
Yes you guys are correct, its a problem with CCSID,
http request node not able to arparse the message xmlnsc message when it contains spain characters.
|
Are you sure the problem was CCSID related and not the encoding property in the PI of your input XML?
_________________
LIFE is a series of complex calculations, somewhere multiplied by ZERO. |
|
| 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
|
|
|
|
