[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2140) Function + MVEL dialect == rule firing in error

[Michal Bali (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBRULES-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12473729#action_12473729 ] 

Michal Bali commented on JBRULES-2140:
--------------------------------------

I am not sure if this helps but the example works fine with SNAPSHOT taken at the following time:
drools-core-5.0.0.20090417.044049-485.jar

> Function + MVEL dialect == rule firing in error
> -----------------------------------------------
>
>                 Key: JBRULES-2140
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-2140
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-compiler, drools-core
>    Affects Versions: 5.0.1.FINAL
>            Reporter: Edson Tirelli
>            Assignee: Edson Tirelli
>             Fix For: 5.1.0.M1
>
>
> REPORTED BY MICHAL:
> ---------------------------------------
> Hi,
> I've encountered a bizarre bug when a function is used together with a declared type and a rule with mvel dialect.
> To reproduce create a default 'New Drools Project' in Eclipse and replace Sample.drl with the following:
> --------------------------------------------------------------------------
> package com.sample
>  
> function void aaa() { // <----- comment this and it will work
> }
> declare SomeBean
> prop : int
> end
>  
> rule "setup"
> dialect "mvel"   // <----- comment this and it will work
> when
> eval(true)
> then
> SomeBean someBean = new SomeBean();
> insert(someBean);
> System.out.println( "setup inserted:" + someBean);
> end
> rule "should never fire"
> salience -20
> when
> not SomeBean()
> then
> System.out.println( "rule that should never fire fired !!!" );
> end
> ------------------------------------------------------------------------
> Run the DroolsTest.java and see that the last rule that should never fire is actually fired. If you comment out the 'aaa' function or change the dialect to 'java' all works fine.
> Note that it breaks on JDK 1.5.0_12 however it works fine on JDK 1.6.0_14.
> Tested on WinXP.
> Is it just my machine or does anybody else see this issue?
> Best regards,
> Michal

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira