Re: prevent infinite loop in orchestration using bts.operation in
- From: Jan Eliasen <eliasen@xxxxxxxxxxxxx>
- Date: Mon, 10 Dec 2007 23:24:54 +0100
On Mon, 3 Dec 2007 06:03:02 -0800, isabelledc
<isabelledc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
So , You can't solve it unless you create a new messagetype and mapWell, something needs to differ the messages your orchestrations
accordingly i suppose
or you could change some promoted property i presume so you can use this...
should pick up from the messages it shouldn't pickup. Unfortunately,
we don't have an "not exists" predicate to use in filters.
Perhaps it's recommended to use direct bound ports mostly for send-portsNo, definately not. using direct bound ports are a nice and beautiful
anyhow?
solution to routing... if you can get it working :-) Pitfalls are too
generic filters, which will let orchestrations and/or send ports pick
up something they weren't supposed to pick up.
I prefer putting as much as possible on receive and sendportsfilter setting on the receive port? Do you mean the receive shape?
anyway...certainly filters. So by NOT USING a direct bound port on the
receiving end I can play with the filter-settings on the receive port,
and by USING a direct bound port on the sending end...i can change theYes.
filter on the send port since the message is put back in the messagebox first.
--
eliasen, representing himself and not the company he works for.
Private blog: http://blog.eliasen.dk
Private email: jan@xxxxxxxxxx
.
- Follow-Ups:
- Re: prevent infinite loop in orchestration using bts.operation in
- From: isabelledc
- Re: prevent infinite loop in orchestration using bts.operation in
- References:
- Re: prevent infinite loop in orchestration using bts.operation in filt
- From: Jan Eliasen
- Re: prevent infinite loop in orchestration using bts.operation in filt
- Prev by Date: Re: properties not being promoted
- Next by Date: Re: BizTalk file read...
- Previous by thread: Re: prevent infinite loop in orchestration using bts.operation in filt
- Next by thread: Re: prevent infinite loop in orchestration using bts.operation in
- Index(es):
Relevant Pages
|