Re: [rules-dev] ClassFieldInspector and Groovy Classes
The following issue (737) was marked as closed, but in the current
SVN the affected code is commented out -- once again rendering Groovy
fact classes inoperable. Can anyone explain why the patch was backed
out? If not, could we reopen JBRULES-737 as a regression or
uncomment the check for "<clinit>"?
Thanks.
Terry
On Mar 14, 2007, at 3:56 PM, Edson Tirelli wrote:
Terry,
Thank you for reporting and providing the patch.
Patch applied:
http://jira.jboss.com/jira/browse/JBRULES-737
[]s
Edson
Terry Laurenzo wrote:
> The attached diff (against 3.0.5 sources) adds a condition to the
> ClassFieldInspector to not analyze methods named <clinit>. For
> some reason, the Groovy compiler is outputing classes that were
> causing this check to choke and throw an IllegalArgumentException
> because of a <clinit> method with ACC_PUBLIC access code.
>
> Applying this patch allows Drools to operate correctly with
> compiled Groovy Fact classes.
>
> This seems like a pretty innocuous change that someone should
> apply to SVN. Unfortunately, it is rather difficult to create a
> test case for it.
>
> Terry Laurenzo
>
> ---------------------------------------------------------------------
> ---
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3124-6000
Mobile: +55 11 9218-4151
JBoss, a division of Red Hat @ www.jboss.com
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev