[rules-dev] An odd couple of patterns

Wolfgang Laun wolfgang.laun at gmail.com
Fri Mar 25 05:05:17 EDT 2011


(Sorry, I didn't read on after the signature.)

On 24 March 2011 20:03, Joe White <Joe.White at recondotech.com> wrote:

>
> Here is an example from our code. $ebs is a List<Map>. Mapping to your
> example the Map is the fact and the combination of BnftInfoCdoe and
> BnftCvgeLevelCode would be the field.:
>
>
>

The positive and negative pattern aren't in conflict in a range of numeric
values, and so yours is not the pattern I'm concerned with.

Notice that I'd put the "not" CE up front.


>   Map(*this*[BenefitsConsts.BenefitResponseEligibility.BnftInfoCode] ==
> 'C',
>
>       *this*[BenefitsConsts.BenefitResponseEligibility.BnftCvgeLevelCode]
> == 'IND',
>
>       *this*[BenefitsConsts.BenefitResponseEligibility.SvcTypeCode] ==
> "30",
>
> *this*[BenefitsConsts.BenefitResponseEligibility.CvgePeriodQlfr] == '25',
>
>       *this*[BenefitsConsts.BenefitResponseEligibility.BnftAmt] *matches*
> "0.*") *from* $ebs
>
>
>
> *not* (Map(*this*[BenefitsConsts.BenefitResponseEligibility.BnftInfoCode]
> == 'C',
>
>           *this*[BenefitsConsts.BenefitResponseEligibility.BnftCvgeLevelCode]
> == 'FAM') *from* $ebs)
>
>
Cheers
Wolfgang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20110325/6a083ca3/attachment-0001.html 


More information about the rules-dev mailing list