Greg – thanks for the extra effort. I am pretty sure you are right, the problem I suspect for me is this –
I have an HttpAdapter on the Receive Location. Now to post HTTP to this location I am using cURL – a command line utility to post HTTP quickly. cURL expects URL-Encoded data and something about this and the encoding is throwing this.
Do you know a better way to post message over HTTP?
[quote:037bea0ce7=\”greg.forsythe\”]I just did a quick test and it worked for me. The message type property is promoted, even if the schema is not deployed and I could set a filter on a send port to route the message based on message type
Could your error be some sort of encoding problem with the test message[/quote:037bea0ce7]