Bug 732726

Summary:	Backport backward chaining fixes from 5.3 branch
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Lukáš Petrovický <lpetrovi>
Component:	BRE (Expert, Fusion)	Assignee:	Mark Proctor <mproctor>
Status:	VERIFIED ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.2.0-ER1	CC:	rzhang
Target Milestone:	---
Target Release:	BRMS 5.2.0.GA
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	726620

Description Lukáš Petrovický 2011-08-23 11:48:36 UTC

Drools 5.2 introduced backward chaining and Drools 5.3 made it actually working. I've talked it over with Mark Proctor and he said that he would back-port the fixes to 5.2 for us. This is a bug to make sure we don't forget about it.

Comment 1 Prakash Aradhya 2011-08-23 19:47:05 UTC

Yes, thats my understanding also talking with Mark Proctor.  
Backward Chaining would be a TP feature in BRMS 5.2.  We cannot call it TP if it is broken.  Should be backported.

Comment 2 Mark Proctor 2011-09-19 05:39:10 UTC

All backward chaining fixes have been back ported. This was non-trivial, as it was a large number of fixes over a period of time.

Comment 3 Lukáš Petrovický 2011-09-19 13:33:25 UTC

The fixes were indeed merged. Should there be any fallout, it will be dealt with in other bzs.