Asanka,

I think I found the root cause of your problem. See https://issues.apache.org/jira/browse/SYNAPSE-402 for more details.

Andreas

On 7 juil. 08, at 20:09, Asanka Abeysinghe wrote:

Hi Andreas,
Problem got solve once I add a namespace for the input message payload.
Asanka A.

Andreas Veithen wrote:
Actually setting the Content-Type header to anything else than "multipart/related" doesn't have any effect. We are in the process of redesigning this. See SYNAPSE-304 and http://cwiki.apache.org/confluence/display/synapse/JMS+Transport+Specifications for more details. What happens here is that the JMS transport fails to parse the message as SOAP or POX and falls back to creating a text wrapper, but I don't see the reason why the SOAP/ POX parsing fails.

Andreas

On 1 juil. 08, at 22:40, Asanka Abeysinghe wrote:


Reply via email to