Bug 1021812

Summary: Handle conflicts when using @position in declared types
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Marek Winkler <mwinkler>
Severity: high 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:18:52 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:
Embargoed:

Description Mario Fusco 2013-10-22 07:16:36 UTC 
declare A
f : int @position(2)
g : int @position(1)
end

declare B extends A
h : int @position(3)
i : int @position(2)
end

The resulting field order may not be deterministic because of

    the clashes (2)
    the missing pos (0)

this is dangerous when used with positional constraints

B( $x, $y, $z, $w ; )
Comment 1 Mario Fusco 2013-10-22 07:17:14 UTC 
Fixed by https://github.com/droolsjbpm/drools/commit/0876a1f6ad9327d42dd1c9a213d6eb7f677f8fe9
Comment 3 Marek Winkler 2013-12-12 17:33:57 UTC 
Verified on BRMS 6.0.0 ER5.