Hi all...

 

We have a situation where we're trying to pass a body with a single element, whose value contains strings of CRLF's.   In this particular case, the CRLF's are meaningful to the receiving service, so cannot be considered XML white space or noise.    Ultimately, we need to deliver them "as is" to the service at the other end, with decimal 013, followed by decimal 010, intact.  

 

Developer is using wsdl2java to generate proxy classes to make the method available and make the SOAP client call.     

 

It appears that somewhere during serialization, the CRLF's are ignored or replaced and ultimately appear at the service as LF's only, as they might in a pure FTP file transfer scenario.  Client happens to be a Windows environment and server is running on BEA at a Linux server.   At one point we believed that escaping the characters per XML as 
 would help, but appears to only work if we can intercept the envelope after creation and just before the send (we did this using a debugging tool, but haven't determined a way to do this in the actual code).

 

Any thoughts or wisdom on how this might be accomplished are appreciated.

 

Ernie

 

 

 

Ernie Ostic

Product Specialist

Office:   732 603 5249

Cell:  617 331 8238

 

Reply via email to