A little followup...
I was able to locate a "Cool XSD Validation Function for Orchestration" in
Alan Smith's "Blogger's Guide to BTS", contributed by Paul Brown.  I built
and deployed this to GAC, plugged it into an expression just after my map an
d
within my Scope, and am catching the XMLSchemaException.  I am then using th
e
SQL Adapter to return the Exception.Message and a rejection flag to my
database, correlating on the TransactionSetControlNumber in the EDI document
.
Life is beautiful.
Thanks again for your INVALUABLE help with this!
--
John

PS.  If you don't know about the "Blogger's Guide," it is located in the
GotDotNet Workspaces area.  Some great info there!


"Matt Milner" wrote:

> You can do some simple validation on your own by using a .net component an
d
> the document schema.  The XLangPart class has a property on it that will
> give you the schema you need to validate the document and there are numero
us
> samples on how to validate a document with an XML schema using the .Net xm
l
> libraries.  There are also settings that you can change to force validatio
n
> of messages at various points in your orchestrations (see Runtime Validati
on
> in the help files) but this is an all or nothing configuration and may be
> more of a perf hit than you want.
>
> If you do this validation yourself, then you can throw and catch an
> appropriate error and handle it in the orchestration.
>
> Matt
>
>
> "JT" <Jthayer@online.nospam> wrote in message
> news:A5400CA2-1C10-478D-B015-3CEDCC734A8C@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]