Dear Thomas
I got the idea. Thanks alot for quick and detailed response.
Ragards,
Dhari
From: tswinde...@nds.com
To: rules-users@lists.jboss.org
Date: Mon, 8 Mar 2010 08:16:31 +
Subject: Re: [rules-users] How to traverse the Collection by index
One of the big challenges of
;-)
Pavel
2010/2/24 Shabbir Dhari sdh...@hotmail.com:
I tried with some thing different and it worked but I don’t want this as I
have many collections in my data structure.
//this works
Membership ( $regDate : regDate)
Segment ( $endDate : endDate )
Segment
Hi W
I know about case sensitivity issue. How can I combine both Order and Item in
one condition. I tried all possibilities but getting syntax error.
For example:
Order ($items : items, $discount : discount 10, Item(grade 3)
from $items) // gives error
Can please code this condition
Segment ( $endDate : endDate, startDate $regDate || startDate $endDate )
even does not work. I am using verstion 5.0.1. All dates are java.util.Date and
values in sample fact are:
regDate = Fri Aug 01 00:00:00 BST 2008
startDate = Tue Sep 01 00:00:00 BST 2009
endDate = Fri Jul 30 00:00:00
I tried
with some thing different and it worked but I don’t want this as I have many
collections in my data structure.
//this works
Membership ( $regDate : regDate)
Segment ( $endDate : endDate )
Segment ( startDate $regDate || startDate $endDate )
//this does NOT work
Dear all
We are developing a financial business application that contains hundreds of
business rules for validations and calculations. In the calculation rules we
change the value of attribute if values past in the request is incorrect e.g.
rule TaxCalc
when
$i : Invoice()
I know this
work around. But I have more than 50 rules using that attribute and it looks
very ugly to put null on every rule and its not single attribute. There are
more than 30 attributes in the bean and using them in LHS. Any other
sophisticated
way?
Date: Tue, 12 May 2009 23:15:54 -0700
(not java.lang.Float)?
-W
2009/5/13 Shabbir Dhari sdh...@hotmail.com
I know this work around. But I have more than 50 rules using that attribute and
it looks very ugly to put null on every rule and its not single attribute.
There are more than 30 attributes in the bean and using them in LHS. Any other
, except, of course, in the rule where you fix and
log the field.
-W
2009/5/13 Shabbir Dhari sdh...@hotmail.com
Well I cant explain you all the issues and requirements here. Simply we dont
have provision to do so. We have to check the null in the rules and log the
message plus other evaluation
Thanks to
all.
The problem we have is that rules will be code by business user. As a developer
I don’t mind putting null check on every rule. But for business user its
unacceptable for checking null for the same attribute in around 50 rules.
Shannon, can you please elaborate more about
Yes - definitely I am using the same version otherwise I'd have exception in
every transaction. But I am getting this very inconsistently. I doubt there is
a bug in RuleBase dieselisation.
From: krishna.bham...@qwest.com
To: rules-users@lists.jboss.org
Date: Tue, 21 Apr 2009 06:29:05 -0600
11 matches
Mail list logo
