Bug 1021812 - Handle conflicts when using @position in declared types
Summary: Handle conflicts when using @position in declared types
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Mario Fusco
QA Contact: Marek Winkler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 07:16 UTC by Mario Fusco
Modified: 2014-08-06 20:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:18:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DROOLS-249 0 Minor Resolved Handle conflicts when using @position in declared types 2013-12-12 17:29:56 UTC

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 3 Marek Winkler 2013-12-12 17:33:57 UTC
Verified on BRMS 6.0.0 ER5.


Note You need to log in before you can comment on or make changes to this bug.