tags:

views:

13

answers:

1

The following is essentially the rule: If the ndoes do not exist then do not continue with the next rule. If the nodes do exist then continue with the next rule.

This is accomplished by setting the priority on the rules and then by "Halt and clear all rule firings" - on the initial check for nodes existing.

I've tested in the rule composer and the first rule is fired. However, this doesn't stop the next rule from firing. It continues and fails because obviously the node is not found in the xml.

Has anybody any ideas why it would continue even though the action specifically say's "halt and clear all rule firings"?

Is there some kind of BizTalk - reset the host instance, restart visual studio trick?

I've done this in another rule and it works fine...

A: 

It seems as though the engine runs all the rules at once. I've managed to get around the problem by using specific XPath for the rules.

Datoon