|
Home > Archive > BizTalk Server Orchestration > February 2006 > Breaking a loop
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]
|
|
| Competitive Dad 2006-02-10, 5:51 pm |
| I've got a Loop in my orchestration that has a decision in it also.
The decision is based on a boolean result from a web service call.
If false, which means a message has not been received by a database, the
thing waits a minute, adds to a loop variable and loops. It does this 3 times.
If true it goes and gets the result. Problem is it is still in the loop so I
need to break out of it to continue on. I can set the loop variable I've
created in this decision branch so that it won't loop again, but that seems a
bit untidy.
Is there a better way of doing this?
Thanks,
Martin
| |
| MaurĂcio Ritter 2006-02-10, 5:51 pm |
| I think that setting the loop variable is the best option you have. Another
option is to put the loop inside a Scope shape with an Exception Handler to
ApplicationException. Inside the loop, when you want to stop processing, just
throw an application exception (I still prefer the loop variable option).
--
MaurĂ_cio Ritter
MCP (Biztalk 2004), MCSD (VC++, VB, VB.NET), MCAD
MCSE (Win2000), MCDBA (SQL2000), MCT years 2002 to 2005
http://www.dotnetmaniacs.com.br
"Competitive Dad" wrote:
> I've got a Loop in my orchestration that has a decision in it also.
>
> The decision is based on a boolean result from a web service call.
>
> If false, which means a message has not been received by a database, the
> thing waits a minute, adds to a loop variable and loops. It does this 3 times.
>
> If true it goes and gets the result. Problem is it is still in the loop so I
> need to break out of it to continue on. I can set the loop variable I've
> created in this decision branch so that it won't loop again, but that seems a
> bit untidy.
>
> Is there a better way of doing this?
>
> Thanks,
>
> Martin
|
|
|
|
|