Re: [rules-users] Using Java Rule Engine JSR-94

JSR-94 is just an API, not an implementation. A bit like if you use JPA, you still need to have an implementation layer such as Hibernate, and DB-specific drivers underneath. The theoretical benefit is that you should be able to swap rule engine implementations such as Drools, JRules, or Blaze, without changing your API code. The reality is that most of these rules engines have a lot of functionality additional to the JSR-94 spec, and may not even be a particularly good fit to it. So using the JSR-94 API means that you need to accept a cut-down interface to the rules engine, which prevents you from accessing much of the functionality that you really need. To evaluate whether it's worth it, take a look at your code. What is the ratio of Drools API code to actual Drools DRL? I'm pretty sure that in any real-world application, re-writing the API code to an alternative platform is trivial in comparison to re-writing all of the rules code. Steve On 16 May 2013, at 10:09, abhinay_agarwal <abhinay_agarwal(a)infosys.com&gt; wrote: