A couple of options occur to me. In either one, the first thing to do is to enable the AllowUnrecognized property of the XML Disassembler so that it doesn’t generate an error if the document schema cannot be found. The second part is discarding unrecognized messages. For this, I can think of two options:
- Set up a second subscription that will get messages from the receive location and route them (so that they don’t get suspended) and then discard them. This could be done by simply dumping them to a folder you clean periodically, or using something like my /dev/null adapter.
- Create a custom pipeline component that runs after the xml disassembler looks for unrecognized messages (not sure exactly how, but I think it can be done) and then simply swallows them.