• From: David Carver <d_a_carver@y...>
• To: "LAKKAM Vinay (AXA-I)" <Vinay.Lakkam@a...>
• Date: Thu, 19 Oct 2006 10:48:25 -0400

LAKKAM Vinay (AXA-I) wrote:
>
> Hi,
>
>  
>
> I need a suggestion for an xml design in my project.
>
>  
>
> We have a requirement to build a rules engine which will be accessed 
> very frequently(almost after every screen) to get a rule result. The 
> rules engine will have about 100 rules, and when we pass the input 
> information it will process again all the rules and returns the matched.
>
>  
>
> I could only think of using a database table to implement this rules 
> engine. For that I need to call DB after each screen to check if any 
> rules matched. But this is going effect the performance of the system. 
> The other way is to get all rules initially, preserve it with message 
> that you send between server and client, and use to get the matched 
> rules whenever needed. But the increased message size will again cause 
> degrade in system performance if the rules size goes big.
>
>  
>
> And new rules will added to the rules engine by admin people, whenever 
> needed.
>
>  
>
> Could you please suggest the alternative ideas to implement this.
>
>  
>
> (We use xml based j2ee framework.)
>

There are several rules engines out there already.   You might want to 
take a look at XRules.org, it's .NET based but the source code is 
available and could be ported over to Java.   If you are using J2ee you 
might want to take a look at JBoss Rules, 
http://www.jboss.com/products/rules

Dave

• Follow-Ups:
  • Re: A design problem
    • From: Rick Jelliffe <rjelliffe@a...>

• References:
  • A design problem
    • From: "LAKKAM Vinay \(AXA-I\)" <Vinay.Lakkam@a...>