ASP.NET Web Services do support literal encoding. But _only_ in
conjunction with document oriented messages!
Any other combination of parameter formatting/overall SOAP formatting is
supported, though ...
Christian
-
.NET XML Web Services Repertory
http://www
of success getting .NET and Apache to talk to each other
with soap encoded data types.
Yours
Phil
- Original Message -
From: "Taz Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 09, 2002 12:12 AM
Subject: XML Literal Encoding Problems with MS .N
I am trying to receive an XML document from a MS .NET
web service. I specified the encoding style as
NS_URI_LITERAL_XML:
call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
There are no parameters. The SOAP response is:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.
Hi Hike,
can you give me an explanation of your service and of your technical
environment.
I am interested in very much, because I´m working on my diploma about "Web
Services"
Since the October I´m workung at this battlefield ;) and for the diploma I
want
to implement a Service with JAVA and the
> Hi all,
>
> I recognized that I had soap 2.1 on the machines that didn't run properly.
> By upgrading to 2.2
> everything woks fine now. I didn't thought it was depending on the
> version.
> But I am really glad that my problem was solved so easily ;-))
>
> Thank you all, you are really doing
It's no problem to transfer "our" Umlaute via UTF-8. The only problem are the tools at
the endpoint you use to show the content. If they understand UTF-8 you will get an
porper result.
ANdreas Ullmann
> Hi all,
>
> my gernan umlauts get scrambled.
> The peculiarity is that I have one solaris
Hi all,
my gernan umlauts get scrambled.
The peculiarity is that I have one solaris machine (2.6) where it works fine
and one solaris machine (2.8)
and one linux box (suse 7.1) where it does not work (all clients, server
runs always on the same machine).
I set the environment variable to LANG=de
