| Roland Jäger 2004-07-01, 7:47 am |
| Hi!
In one of his blogs Scott Woodgate describes a generic web service that
can accept any type of XML document
(http://blogs.msdn.com/scottwoo/arch.../03/147743.aspx). I tried
the example and it works perfectly.
However, I can't get it working with a Web Service port while using the
XML Reveive Pipeline. My intention was to use the pipeline to
disassemble the message to get the namespace (message type) and then put
it into the appropriate orchestration by filtering for the message type.
When using a normal file port, this works fine. The message is decoded
and the orchestration with the correct filter picks up the message.
However, when I switch to a web service port (request-response with
string type response) I get a pipeline exception: 'Document type
"order" does not match any of the given schemas'. I'm still submitting
the same message (in a soap envelope of course) and the schema is still
deployed.
Switching to a pass through pipeline solves the problem but since the
message type cannot be found I end up with a routing error.
Strangely, if I remove the schema with the namespace "order" from my
schema assembly, the error is also solved (with the XML pipeline
activated) and the message is correctly delivered to the orchestration.
But since my mappings expect a schema with a different namespace now,
all mappings fail...
Is there any other way (tried property schema as well) to route the
incoming messages to their appropriate orchestrations?
Thanks for your support,
Roland
|