A colleague  of mine asked: “What kind of exception is thrown from the xml validation pipeline component?”. The reason was that she had to execute xml validation from within an orchestration, using as receive pipeline. Depending on whether the data was valid or not different actions would be taken. The solution was to put the pipeline execution in a scope and add exception handling. However; in order to catch only validation errors we had to know what kind of error is thrown. I set up this little orchestration:

try..catch

The answer is that it throws an Microsoft.XLANGs.Pipeline.XLANGPipelineManagerException, which is caught in the first exception block.

So, now you know.