Bug 748741 - Operator isA is not working
Summary: Operator isA is not working
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Nobody
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 08:46 UTC by Tomas Schlosser
Modified: 2022-08-12 04:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Simple reproducer (1.48 KB, application/x-zip-compressed)
2011-10-25 08:46 UTC, Tomas Schlosser 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomas Schlosser 2011-10-25 08:46:38 UTC 
Created attachment 530031 [details]
Simple reproducer

Description of problem:
If I try to use isA operator the condition is always evaluated to false.

Version-Release number of selected component (if applicable):
BRMS-5.3.0.dev4

How reproducible:
Every time

Steps to Reproduce:
1. run attached reproducer
  
Actual results:
Starting execution...
Student is attending Masaryk University
Finished...

Expected results:
Starting execution...
Student is attending Masaryk University
Person is a student: <result of toString method>
Finished...

Additional info:
Comment 2 Edson Tirelli 2012-02-01 18:37:05 UTC 
There was a problem in the provided test case, as it was missing the update() call after donning the trait in the first rule's consequence. 

After fixing the test, everything is working. I added it to the codebase:

https://github.com/droolsjbpm/drools/commit/be473a65b185031dc68260e4d5a80a2459e5dceb#L1R1044

https://github.com/droolsjbpm/drools/commit/be473a65b185031dc68260e4d5a80a2459e5dceb#L2R1
Comment 3 Ryan Zhang 2012-02-15 09:13:03 UTC 
Please verify the issue on 5.3 ER4.
Comment 4 Tomas Schlosser 2012-02-22 11:59:22 UTC 
I have fixed our test as well and it works now.
Note You need to log in before you can comment on or make changes to this bug.