08-27-04 11:07 PM
When you put a filter on your send port, and then enlist it, you get a
subscription for that send port, so each port will have a subscription of
its own. When your send port group has a filter it has the subscription and
then sends the message to each send port. The filters for those send ports
do not come into play at that time.
It sounds like what you want is a dynamic port or a role link. A send port
group is really for sending to a group of send ports, all of them. If you
have two ports and you need to decide which to use, then you want a dynamic
port. You might also want to use role links in your orchestration to
accomplish this if the ports differ by who or what is filling the role.
Matt
"Andrew" <biztalkq@mail9.com> wrote in message
news:412f7b89$0$52217$65c69314@mercury.nildram.net...
> I'm having the following problem with BizTalk Server 2004:
>
> I have a Send Port Group with two Send Ports. Each Send Port has a filter
> on a promoted property, and they are mutually exclusive. I expected that
if
> the Send Port Group picks up a message, only one of the Send Ports will
send
> it.
>
> However, when I send via the Send Post Group BOTH Send Ports send the
> message, even though the filters are mutually exclusive.
>
> I tested that the filters were correct by removing the Send Port Group and
> adding a Receive Port that publishes the message. Only one of the Send
> Ports sends the message, so the filters work as expected.
>
> Why am I getting this behaviour? Is it by design?
>
> Regards
>
> Andrew
>
> P.S.
> The reason for having the Send Post Group was so that I can bind to port
> when sending from and orchestration.
>
>
>
[ Post a follow-up to this message ]
|