RE: Resolve Party question

From: Chris (Chris_at_discussions.microsoft.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 13:25:02 -0700

Thanks Gilles for this quick answer...

2) Makes sense, that's what I'm leaning to.

1) The problem is that if the out of the box Party Resolution comp cannot
authenticate it will throw an exception, and my custom resolution one is
never called. Did I miss something in your explanation?

Thanks,
Christian.

"Gilles [MSFT]" wrote:

>
> >For example if I use the default "Party Resolution" comp as well as a custom
> >one where I use my own logic. I would like then to rely on certificate (using
> >the default Party resolution comp) but if this fail I would like then to use
> >the custom one. If the incoming doc is authenticated using certificate, I
> >don't want then the custom comp to be executed.
>
> There are a few ways to do this:
>
> 1) Detect (by accessing the message context) if the out of the box party resolution component did its job sucessfully or not.
> If it did, proceed and perform your processing, if it did not, just do not do anything.
>
> 2) Have your party resolution custom component contain an instance of the out of the box party resolution component.
> Now, you need only one party resolution component in the pipeline. The coude will delegate party resolution to the out of the box
> component, detect if this worked (by looking at the context) and decide if further processing is needed.
>
> Thanks,
> -Gilles.
>
>