Author |
Message
|
WMBSAM |
Posted: Tue Nov 17, 2009 12:19 pm Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
there is some update in this issue. if we see at the error which is:
Code: |
'Error Making SOAP JNI Call: Axis2Requester_processResponseMessageSync', 'Axis2Requester_processResponseMessageSync', 'org.apache.axis2.AxisFault: Character Set Encoding from transport information [UTF-8] does not match with character set encoding in the received SOAP message [iso-8859-1]' |
i saw the log file from the TCP-IP monitor i found that there is no encoding specified in the transportation header(httpresponse header)which says Content-Type: text/xml which actually should be Content-Type: text/xml; charset=iso-8859-1 As the encoding is not specified in the transportation header by default broker is assuming it ti be UTF-8 format. SO that is the reason we are receiving the below error.
ERROR::"'org.apache.axis2.AxisFault: Character Set Encoding from transport information [UTF-8] does not match with character set encoding in the received SOAP message [iso-8859-1]"
So my quetion is:
Is ther any way that we can set the Http response header Content type to Content-Type: text/xml; charset=iso-8859-1 ???
Becoz as soons as it reaches the Soap request node the above error occurs
 |
|
Back to top |
|
 |
WMBSAM |
Posted: Tue Nov 17, 2009 12:26 pm Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
Sorry just thought to inform that the whole request and response works fine in SOAPUI so i think there should be something which should make things happen for broker too |
|
Back to top |
|
 |
mgk |
Posted: Tue Nov 17, 2009 2:50 pm Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1647
|
OK, so today the SOAP Request node requires that the response message Content-Type charset in the http headers matches the encoding in the xml declaration (if there is one). If there is no charset in the content-type then UTF-8 is assumed. This works fine unless you have an explicit encoding in your message (as in this case).
Therefore, you seem to have a couple of choices:
1: send a charset of iso-8851-1 for the content-type
2: do not send back an xml declaration at all in the body.
Kind Regards, _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Last edited by mgk on Wed Nov 18, 2009 7:59 am; edited 1 time in total |
|
Back to top |
|
 |
WMBSAM |
Posted: Tue Nov 17, 2009 3:27 pm Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
Quote: |
send a charset of iso-8851-1 for the content-type |
You mean to say that i set the
SET OutputRoot.Properties.ContentType = 'text/xml; charset=iso-8851-1';
in the request message before i make a SOAP webservice call??
Quote: |
do not send back an xml declaration at all in the body. |
Do you mean to say that the response i receive from the Webservice should not have the XML declaration at all or in the should not have the xml decalration in the request message that i send wen i invoke the webservice???
Becoz if it is response message it is out of my reach i have tried make understand the issue with the those webservice guys (the webservice to which i making the call) and they have tested their webservice with SOAP UI and thay expect it to work with WMbroker. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Nov 17, 2009 8:51 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20767 Location: LI,NY
|
Why not try it this way:
Do not set any information about xml encoding.
Set OutputRoot.Properties.CodedCharSetId = 1208 ; -- UTF-8
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mgk |
Posted: Wed Nov 18, 2009 5:58 am Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1647
|
I think you should raise a PMR for this, and mention this thread in the PMR... _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
WMBSAM |
Posted: Wed Nov 18, 2009 11:10 am Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
Believe me i have raised the PMR on this issue long back only difference is i have not mentioned this thread in the PMR  |
|
Back to top |
|
 |
WMBSAM |
Posted: Fri Nov 20, 2009 11:14 am Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
just thought to add update for this issue as a temporary fix is it a good idea to do a opaque parsing on the message response encoding so that after we receive the message in the soap request node then we may reparse in the way we wanted????  |
|
Back to top |
|
 |
WMBSAM |
Posted: Thu Dec 03, 2009 4:34 pm Post subject: |
|
|
 Voyager
Joined: 02 Oct 2009 Posts: 90 Location: Atlanta
|
As an update to this thread just thought to inform you all that a temporary fix has been done to solve this issue
This time Soap request node instead of directly making a call to the webservice it will make a call to another message flow which has http request node (Tunneling Process As directed by IBM) . The webservice call is invoked using http request node and then after we receive the response using the http header change the response content type to "iso-8859-1" and then send back to the main flow
SOAP request node-->(Tunneling Flow)Http input node-->http request node-->http header(change the content type to iso-8859-1)-->http reply
and it finally worked (temporary fix if i am not wrong) !! |
|
Back to top |
|
 |
|