NAck Processing using an Orchestration

I saw this NACK example, and had to think about a "loose end" I still haven't found an answer for yet, so I thought I'd ask you! A few questions: 1. Did you create the NACK.xsd yourself by hand? If not, how did you create it? 2. Did you ever try to map the NACK message as an outbound map on an incoming request-response port? See my explanation of this question below. We're talking BTS06R2, not BTS04 here. I once had to deal with a webservice client that expected a valid response message, even in the case of exceptions (I didn't design it!). I wanted to deal with this using only message-routing and WCF-BasicHttp adapters (the webservice request-response call was forwarded to another system by BizTalk using only message routing & WCF adapters). Dealing with all kind of exceptions becomes hard, because for each fault message published by the forwarding solicit-response port, you need to specify an outbound map on the incoming request-response port (at this point in time I really think it would have been better to use an orchestration and use general exception handling). One of those maps was a NACK-to-response map, in case the forwarding WCF adapter couldn't deliver the request. Hopefully this explains my question 2 above. Thanks, Bram.