|
Home > Archive > BizTalk Server General > August 2005 > testing policies in Business Rule Composer
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 |
testing policies in Business Rule Composer
|
|
| PeterW 2005-08-02, 2:54 am |
| I have created a Policy and RuleSet in Business Rule Composer comprising 95
rules.
I test it against a document which contains 20 elements that should evaluate
to true in a Match.
The test arbitrarily uses rule 'r15' for the right operand and no other
values. It correctly uses the 20 values for the left operand. The value
'r15' is not one of the 20 so a true test result is never found. The value
of 'r15' never changes.
What is it that I am missing to make it use the full set of 95 rules for the
right operand.
At the moment the rule engine trace shows that it does 22 assertions, 2 of
which test parts of the XPath before we reach the records or elements that
are significant. It then does 22 retracts.
I would have expected it to do that for all 95 rules, so 22 * 95 assertions.
Any help would be appreciated.
cheers
--
PeterW
| |
| PeterW 2005-08-02, 7:50 am |
| Sorted this out by referencing a rules table and adding an equals test for
each rule.
It now fires true where required.
cheers
--
PeterW
"PeterW" wrote:
> I have created a Policy and RuleSet in Business Rule Composer comprising 95
> rules.
>
> I test it against a document which contains 20 elements that should evaluate
> to true in a Match.
>
> The test arbitrarily uses rule 'r15' for the right operand and no other
> values. It correctly uses the 20 values for the left operand. The value
> 'r15' is not one of the 20 so a true test result is never found. The value
> of 'r15' never changes.
>
> What is it that I am missing to make it use the full set of 95 rules for the
> right operand.
>
> At the moment the rule engine trace shows that it does 22 assertions, 2 of
> which test parts of the XPath before we reach the records or elements that
> are significant. It then does 22 retracts.
>
> I would have expected it to do that for all 95 rules, so 22 * 95 assertions.
>
> Any help would be appreciated.
>
> cheers
> --
> PeterW
|
|
|
|
|