For data manipulation you can use something like apache camel. To
transform the information and then make inferences over it.
Greetings
- CTO @
http://www.plugtree.com
- MyJourney @
http://salaboy.wordpress.com
- Co-Founder @
http://www.jbug.com.ar
- Mauricio "Salaboy" Salatino -
On Jun 8, 2010, at 15:45, Betto Bardi <betto.bardi(a)yahoo.com> wrote:
Hi all,
We recently implemented Drools in a mortgage application process.
The primary task of the business rule engine was to determine the
fraud risk of an application. The application is delivered in XML
format. We noticed that we were implementing a lot of data
manipulation actions in the drl file itself. For example, the
calculation of total income by calculating the sum of a number of
elements or calculating the distance between two geo-locations based
on zip codes. The actual evaluation rules acted on this 'derived'
information.
When looking back the drl file contained a lot of code and looked
pretty complicated compared to the actual evaluation rules. My
question is, what is your opinion on data manipulation or
transformation within the drl file? If the drl file is not the best
place for this, what would you suggest for data manipulation?
Thanks,
Betto
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users