Hi, Just some comments about the convert to string workaround for XML documents. Though XML documents may look like strings, they are in fact binary data, so even if converting the data to string may help to work around an existing issue, it can cause other issues with specific XML documents. This will specifically happen if the document encoding is not the same as the default encoding of the platform (e.g. platform default encoding is ISO-8859-1 whereas the document is UTF-8 encoded (or vice versa)). In that case all documents containing non-ASCII characters will be destroyed by converting a byte-like representation into a character-like representation (e.g. file to string).
So if there is some type converter issue the best solution would be to analyze and resolve that issue. If you need a workaround, the second best solution is to convert the data to byte[] not to String, this will at least not destroy the encoding (and the BOM). Best regards Stephan -----Original Message----- From: aioria3077 [mailto:aioria3...@gmail.com] Sent: Samstag, 20. September 2014 00:27 To: users@camel.apache.org Subject: Re: please help with transformation of a response by xslt if the call to the original web service, the change will dataFormat MESSAGE by PAYLOAD, The error is: The PayLoad elements cannot fit with the message parts of the BindingOperation. Please check the BindingOperation and PayLoadMessage. I make the first transformation successfully receiving the REQUEST as dataFormat PAYLOAD, I realize that a change to MESSAGE in the original WS call is where the transformation does not work, There is some problem the xslt with MESSAGE dataFormat being that before sending the body convert STRING -- View this message in context: http://camel.465427.n5.nabble.com/please-help-with-transformation-of-a-response-by-xslt-tp5756711p5756757.html Sent from the Camel - Users mailing list archive at Nabble.com.
