Probably less people are testing against
.NET right now. We do have tests that did pass but we’ve also seen some
issues with the player (well also the compiler). The issue that we had
internally was one of line-endings where the XML was mixed in using Windows
line endings (CRLF or \r\n) and Unix (LF or \n). Any way of checking how the
service is coming back (I’d assume since it’s .NET that it’s
CRLF)?
Matt
From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Hansen
Sent: Tuesday, November 29, 2005
10:06 AM
To: [email protected]
Subject: [flexcoders] Flex2 ::
XML-RPC (char replacement nuisance)
Hi list,
I'm doing some Xml RPC to .net backend, and having problems with char
replacements.
I call the service, and it replies something like:
<?xml version="1.0" encoding="utf-8"?>
<tag>
</tag>
where e.g., < is replaced by <
As a result flex do _not_ decoding into the desired object-array.
If a do a .aspx page that write the xml to the document stream i receive
<?xml version="1.0" encoding="utf-8"?>
<tag>
</tag>
and all is well.
If a do a .net webservice, the payload (i.e. the result) is also
'char-replaced' and once again flex2 chokes. If I do a .net client that
connects to the webservice all is well.
Who's at 'fault' here? and is there a way to fix it without writing a custom
xmlDecoder? (either on .net or flex2)
Am I really the only one that have had problems with this or am I stupid (gotta
be realistic sometimes :o)
Cheers
-michael
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
|
- RE: [flexcoders] Flex2 :: XML-RPC (char replacement nuisanc... Matt Chotin
-
