[jboss-jira] [JBoss JIRA] (DROOLS-290) Can't parse condition as FieldConstraintDescr in 5.5.0
Davide Sottara (JIRA)
jira-events at lists.jboss.org
Mon Oct 7 23:26:02 EDT 2013
[ https://issues.jboss.org/browse/DROOLS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12811393#comment-12811393 ]
Davide Sottara commented on DROOLS-290:
---------------------------------------
Constraints are handled differently in 5.5 as opposed to 5.0. In later versions, you can have "free-form" constraints as opposed to simpler <Field OP Value>.
This is not a bug. Are you manipulating the Descr tree yourself? Those classes have never been part of the public API, as far as I know
> Can't parse condition as FieldConstraintDescr in 5.5.0
> ------------------------------------------------------
>
> Key: DROOLS-290
> URL: https://issues.jboss.org/browse/DROOLS-290
> Project: Drools
> Issue Type: Release
> Security Level: Public(Everyone can see)
> Environment: jdk1.6.0.25
> Reporter: Paul Qing
> Assignee: Mark Proctor
>
> hi everyone,
> I met a issue when I upgrade drools from 5.0.1 to 5.5.0. when I parse a rule in the 5.5.0. It will parse condition as ExprConstraintDescr. However,It can parse this condition as FieldConstraintDescr in the 5.0.1. I don't know that this is a bug or not. the rule is as following:
> rule "guy_13"
> when
> $g:Guy(age==13)
> then
> return true;
> end
> the root cause is the parser has parsed "$g:Guy(age==13)" as ExprConstraintDescr in the 5.5.0 and it can work in the 5.0.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list