Groovy was important pre drools 3, when much of the rule logic was in
the semantics of the dialect - but since drools 3(!) that hasn't
really been the case, but it is certainly possible.
Sent from my phone.
On 11/11/2009, at 10:29 AM, Mark Proctor <mproctor(a)codehaus.org> wrote:
Tom Davidson wrote:
>
> Hello,
>
> We are a shop using Groovy and Drools to enable end users to write
> business logic (rules and utility libraries). I was wondering if
> there are any plans to resurrect Groovy as a dialect? We may be
> interested in contributing to such an effort. Can anyone point me
> in the right direction of how to implement a dialect? I looked at
> the Dialect interface and the Java and MVEL implementations a bit,
> but there seems to be a lot of code there. Any guidance on what the
> minimum set of functionality is needed to get things working at a
> basic level?
If you follow how we hook in MVEL that should cover it. We have no
direct plans to resurrect Groovy, as MVEL imho provides everything
we need and is type safe. As we start to add more verification and
anlaysis to Drools type safety will be important.
Mark
>
> Thanks,
> Tom Davidson
>
>
>
> Tom Davidson
> Principal Engineer
> tomd(a)fidex.com
> w: 858.457.3836
>
> <mime-attachment.gif>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4593 (20091110) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
>
http://www.eset.com
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev