Writing my own deserializer

["Wilkins, Craig" <cw...@akamai.com>]

I am looking for some advice on how to write my own deserializer.  

At the very least I am looking for some high-level guidance or steps on how
to write my own deserializer for XML Elements, but if you think that you can
help with my problem, please offer additional suggestions.

My Problem:
Our SOAP service accepts one XML Element parameter.  When this Element is
serialized passed over the wire and then deserialized at the server, all of
the carriage returns that were in the data have been replaced with spaces.
The data that is being passed is well formatted with and carriage returns,
which need to be maintained and entered into the back-end system by our SOAP
service.   

It appears through the TCPTunnelGUI that the carriage returns are still
there on the wire, but if my SOAP service prints them out, the entire text
is on one line and all bunched together.

Example - The following input:
"Steps to send email
1)  Type the text that you want to send
2)  Send the email"

Turns into the following output:
"Steps to send email 1)  Type the text that you want to send 2)  Send the
email"

My thought is that I have to write my own deserializer because there is a
bug that replaces carriage returns with spaces in the default one.  I am
looking for assistance in going about this task.  

Additional helpful info would be the SOAP class file that is responsible for
the default deserializing of XML Elements?  I think that if I found this, I
could maybe find the bug or use it to model my own deserializer after.

Please help!!