It seems as if your rules will fit nicely into a decisiontable.

Sent from my HTC (Android)

On Jan 30, 2010 7:58 PM, "kashif10" <kash452@yahoo.com> wrote:


Thanks edson for you nice advise.
It really reduce the memory uage from 400 mb 70 mb..

 compareDiagnosis(  valueName[0] in ("Heart Failure") ||
 (valueCode[0] in
("402.01","402.11","402.91","402.01","402.03","402.11","402.13","402.91","402.93",
"428.0 - 428.9") , valueCodeSystem[0] == "2.16.840.1.113883.6.2" )    )


Here I have some questions.

i) we have to iterate whole valueName not only [0]. How we can do it.

ii) we have not only simple valueCode matching, we can have
  a) Range in code such as 428.0 - 428.9, so any thing in WM having
valueCode b/w this range should match.
  b) but we can't use simply numbers , we have to use String as we can have
code having alphabet such as "V32.4"
   c) we can have wild card usage too. e.g code in Rule can be "V2*" which
can be match any thing at the place opf asterik in WM valuCodes.

 I see that Rule engine do introspection & call get methods of the fields &
can do simple condition maching like ==, <, >etc.  But mostly we have some
complex logic in matching like I told you in pt ii) of valuecode matching.
I think only sol is to call methods which will comes inside eval() & If we
start usig it for long rules. rules will never load & stuck :(...

Need your expet  advise for those long & complex rules.

Thanks


--
View this message in context: http://n3.nabble.com/Weblogic-rules-to-Drools-rules-tp126265p178895.html

Sent from the Drools - User mailing list archive at Nabble.com. ____________________________________...