I'll add my two cents--a few months ago, I had a project where we were sending
SOAP messages to an application using Tibco BusinessWorks' built-in SOAP
support to receive them. We ran into BOM issues when we used UTF-8, and
finally switched to UTF-16 to get it to work. It's probable that there was
another way around the problem, that we didn't discover, but it was incredibly
helpful to be able to switch encoding so we could verify that the character set
encoding was in fact the problem.
Meghan Pietila
Granite Consulting
"Tom Jordahl" <[EMAIL PROTECTED]>
08/04/2005 06:33 AM
Please respond to axis-dev
To: [email protected]
cc:
Subject: RE: [Axis2] SOAPEnvelope with XML declaration?
I think Ashutosh was talking about the character set encoding in the XML
declaration at the top of the SOAP XML to something other than utf-8.
I was never quite clear why users wanted to turn on/off the XML
declaration in Axis 1.x but they did (so be prepared). Being able to
set the charset of the XML seems like somebody is going to want to do
that though.
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
Sent: Friday, July 29, 2005 1:45 AM
To: [email protected]
Subject: RE: [Axis2] SOAPEnvelope with XML declaration?
>Hi All,
>In current SOAPEnvelope that we come up with, is there some capability
to
>specify if we want to write xml declaration at top or not
I think we don't have that.
>
> and what encoding we want to provide?
SOAP encoding support is not in the code, at all.
-- EC
>-Ashutosh
