Bug 1010281

Summary: Importing a domain class named "Exception" raises an ambiguity exception during RHS compilation
Product: [Retired] JBoss BRMS Platform 6 Reporter: Mario Fusco <mfusco>
Component: BREAssignee: Mario Fusco <mfusco>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Schlosser <tschloss>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0   
Target Milestone: ER4   
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:20:18 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-09-20 12:41:05 UTC
If a user class named Exception is used,

import my.own.domain.Exception

rule "Foo"
when then end

the RHS compilation process resolves "Exception" to that name
rather than to java.lang.Exception

>> Rule compilation error [Rule name=Foo] :
{if import * is used }

The type Exception is ambiguous
{if explicit import is used }

Exception is not Throwable

Comment 1 Mario Fusco 2013-09-20 12:46:22 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/2fe546dbd

Comment 2 JBoss JIRA Server 2013-09-20 12:47:34 UTC
Mario Fusco <mario.fusco> updated the status of jira DROOLS-253 to Resolved

Comment 4 Tomas Schlosser 2013-10-17 15:48:25 UTC
Verified in BRMS 6.0.0.ER4.