Yes unicode space would be seen by the server. But maybe your server should be
handling all the fancy unicode characters?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Chris Martin wrote:
Yeah, I can do that. I'll use some trace statements to rule out the
debugger.
Would usin
Yeah, I can do that. I'll use some trace statements to rule out the
debugger.
Would using Unicode space mean that the service layer would also have to be
expecting a Unicode string value? Hoping to only have to take care of
things o my side. And prettyPrinting only seems to be formatting the bo
prettyPrinting could affect debugger output so be sure you have determined
the problem.
Can you create a simple test case that calls the Soap decoder directly
with some XML? If so, file a bug.
Have you considered using Unicode space?
-Alex
On 2/19/14 12:14 PM, "Chris Martin" wrote:
>Okay, di
Okay, did some more poking and I need to update my observation. I thought
it was the resetting of ignoreWhitespace that was causing things to
revert. Actually it was the resetting of the prettyPrinting setting to
it's original value (of true) at line 175. So ultimately my current
workaround is t
So, I've run into this problem back in Flex 3, and did some "interesting"
things to get around it. I'm now wondering if either a.) it was a true
problem in the SDK and I needed to keep my workaround or b.) I just never
truly understood how to get this to work properly without "hacking it"
Problem
