This is a problem I have not found a clean solution yet.
You can remove the unwanted properties yourself,
or use the MPS component (in servicemix-components),
which can be used to set / copy / remove properties.
Some components can also be configured to copy or not
copy the properties from a message to the other, but it really
depends on the component used. I think the best solution
may be to configure that on the servicemix-http component
so that i does not send unwanted properties in the exchange.
Could you please raise a JIRA for that ?
On 12/27/06, Maxim Y. Tebenev <[EMAIL PROTECTED]> wrote:
I've found a workaround for this issue. Intermediate endpoint added. That
endpoint runs Groovy script as following:
outMessage.setProperty("javax.jbi.messaging.protocol.headers", null)
outMessage.setContent(inMessage.getContent());
Are there solution for that without such a trick?
Best regards, Maxim Tebenev.
--
View this message in context:
http://www.nabble.com/consumer-to-provider-SOAP-transformation-tf2883435s12049.html#a8063979
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
