Bug 1021803

Summary: Property reactivity does not work with positional/unification constraints
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Winkler <mwinkler>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.0   
Target Milestone: ER5   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:15:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mario Fusco 2013-10-22 07:06:31 UTC 
Positional and/or unification constraints are interpreted as either bindings
or constraints, depending on the whether the variable is already bound or not. The user is expected not to have to care about the difference.

...
Person( $name; $age := age )
...

If the pattern type is @propertyReactive, however, the actual decision
between binding and constraint WILL make a difference, possibly forcing
the user to use @watch()
Comment 1 Mario Fusco 2013-10-22 07:07:27 UTC 
Fixed by https://github.com/droolsjbpm/drools/commit/3361ff876ca3bdd9d28cad3997c576d7211bd748
Comment 3 Marek Winkler 2013-12-12 17:05:25 UTC 
Verified on BRMS 6.0.0 ER5.