|
Home > Archive > BizTalk Server Orchestration > August 2004 > Probing interface for pipeline component
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Probing interface for pipeline component
|
|
| Norton 2004-08-27, 6:06 pm |
| If I write a custom pipeline component with the IProbing interface, does
that mean that I will be able to change the execution mode in some of the
pipeline stages (that don't appear to allow changes now)?
Thanks.
Norton
| |
| Devdutt Patnaik 2004-08-27, 6:06 pm |
| It means that depending on the return value from the Probe method, the
Execute method will or will not be executed.
"Norton" wrote:
> If I write a custom pipeline component with the IProbing interface, does
> that mean that I will be able to change the execution mode in some of the
> pipeline stages (that don't appear to allow changes now)?
>
> Thanks.
>
> Norton
>
>
>
| |
| Norton 2004-08-27, 6:06 pm |
| Sorry, I don't understand your answer.
Right now if I look at most of the Execution Modes in the pipeline stages,
they are greyed out. Only the one for the dissassembler is set to First
Match.
If I were to write multiple Mime decoder components (for example) and if I
used the probe interface, will I then see the Execution Mode change to First
Match?
Thanks.
Norton
"Devdutt Patnaik" <Devdutt Patnaik@discussions.microsoft.com> wrote in
message news:34F5D1FD-0345-4FB8-A9CD-30C8D6AC3ED4@microsoft.com...[vbcol=seagreen]
> It means that depending on the return value from the Probe method, the
> Execute method will or will not be executed.
>
> "Norton" wrote:
>
| |
| Gilles [MSFT] 2004-08-27, 6:06 pm |
| Hello,
>Right now if I look at most of the Execution Modes in the pipeline stages,
>they are greyed out. Only the one for the dissassembler is set to First
>Match.
>
>If I were to write multiple Mime decoder components (for example) and if I
>used the probe interface, will I then see the Execution Mode change to First
>Match?
Probing requires FirstMatch execution mode:
http://msdn.microsoft.com/library/e....asp?frame=true
<quote>
Components may implement this interface when they need to have probing functionality, when they need to be able to check the beginning part of data to
determine if the format of message is known to the component. Probing functionality is utilized only in stages with FirstMatch execution mode. This behavior is
used when several parser components are placed in one pipeline. The first parser that can recognize the message format is executed.
</quote>
This page http://msdn.microsoft.com/library/d...g_pipe_yvmd.asp explains execution modes
with the respect to stages:
<quote>
Note In this release of BizTalk Server 2004, all the stages in a send pipeline and all stages except Disassemble in a receive pipeline have the value of the
Execution Mode property set to All. The value of the Execution Mode property in the Disassemble stage is set to FirstMatch. You cannot change the
Execution Mode property of a stage.
</quote>
Thanks,
-Gilles.
| |
| Devdutt Patnaik 2004-08-27, 6:06 pm |
| I don't think Execution Mode of a stage can be changed. If you want the
message to exit the stage after the first matching component processes it,
you might want to put this group of components in the disassemble stage.
Regards
Dev
"Norton" <thenortonz@hotmail.com> wrote in message
news:edGEfa1iEHA.3664@TK2MSFTNGP11.phx.gbl...
> Sorry, I don't understand your answer.
>
> Right now if I look at most of the Execution Modes in the pipeline stages,
> they are greyed out. Only the one for the dissassembler is set to First
> Match.
>
> If I were to write multiple Mime decoder components (for example) and if I
> used the probe interface, will I then see the Execution Mode change to
First
> Match?
>
> Thanks.
>
> Norton
> "Devdutt Patnaik" <Devdutt Patnaik@discussions.microsoft.com> wrote in
> message news:34F5D1FD-0345-4FB8-A9CD-30C8D6AC3ED4@microsoft.com...
does[vbcol=seagreen]
the[vbcol=seagreen]
>
>
| |
| Devdutt Patnaik 2004-08-27, 6:06 pm |
| Lemme re-phrase my above post:
If you have a stack of decoder components, then i think all of them should
implement IProbeMessage, and the logic inside the Probe() method should
ensure that only one of those components is ever executed for one message.
Regards
Dev
"Devdutt Patnaik" <devdutt.patnaik@amicore.com> wrote in message
news:OBsBrU5iEHA.2760@TK2MSFTNGP15.phx.gbl...
> I don't think Execution Mode of a stage can be changed. If you want the
> message to exit the stage after the first matching component processes it,
> you might want to put this group of components in the disassemble stage.
>
> Regards
> Dev
>
> "Norton" <thenortonz@hotmail.com> wrote in message
> news:edGEfa1iEHA.3664@TK2MSFTNGP11.phx.gbl...
stages,[vbcol=seagreen]
I[vbcol=seagreen]
> First
> does
> the
>
>
| |
| Martijn Hoogendoorn 2004-08-27, 6:06 pm |
| On Thu, 26 Aug 2004 14:50:23 -0400, Devdutt Patnaik wrote:
[vbcol=seagreen]
> Lemme re-phrase my above post:
> If you have a stack of decoder components, then i think all of them should
> implement IProbeMessage, and the logic inside the Probe() method should
> ensure that only one of those components is ever executed for one message.
>
> Regards
> Dev
>
> "Devdutt Patnaik" <devdutt.patnaik@amicore.com> wrote in message
> news:OBsBrU5iEHA.2760@TK2MSFTNGP15.phx.gbl...
> stages,
> I
Hi Norton,
I think Devdutt is right, currently the execution mode of a given stage
cannot be altered, and implementing IProbeMessage is only useful in the
Disassembler stage. I think they've incorporated that execution mode for
future implementations, or they might even make it available in a
servicepack.... Anyways, the XmlDisassembler component nicely implements
IProbeMessage, for an example, have a look at that component.
HTH,
Martijn Hoogendoorn
|
|
|
|
|