Bug 724205 (BRMS-148) - Use of reserved word as bound variable in a pattern results as NPE
Summary: Use of reserved word as bound variable in a pattern results as NPE
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-148
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.0.0 GA,5.0.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: future
Assignee: Edson Tirelli
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-07 12:03 UTC by nwallace
Modified: 2009-09-16 14:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Eclipse 3.2, Windows XP
Last Closed: 2009-09-16 14:57:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-148 0 None Closed Use of reserved word as bound variable in a pattern results as NPE 2011-09-02 00:40:03 UTC
Red Hat Issue Tracker JBRULES-1287 0 None Resolved Use of reserved word as bound variable in a pattern results as NPE 2011-09-02 00:40:03 UTC

Description nwallace 2009-07-07 12:03:32 UTC 
Date of First Response: 2009-09-10 00:16:01
securitylevel_name: Public

example:

rule "This generates an NPE"
	when
		result : ReservedWordNPEFact(data < 15)
	then
		result.setData(new Integer(1));	 
end

At least in the eclipse IDE, this generates an NPE.  Change result to something like:


rule "This generates an NPE"
	when
		f: ReservedWordNPEFact(data < 15)
	then
		f.setData(new Integer(1));	 
end

and it goes away.
Comment 1 nwallace 2009-07-07 12:04:47 UTC 
Link: Added: This issue is related to JBRULES-1287
Comment 2 nwallace 2009-07-07 12:06:23 UTC 
Link: Added: This issue related JBRULES-1287
Comment 3 nwallace 2009-07-07 12:22:49 UTC 
Link: Removed: This issue is related to JBRULES-1287
Comment 4 nwallace 2009-09-01 12:15:30 UTC 
Fix in place.
Comment 5 David Le Sage 2009-09-10 04:16:01 UTC 
For the errata in the release notes, we require details of:


1.  the FIX (what was changed in the new parser) and 

2.  CONSEQUENCES of the fix (how this benefits users.)


Dot points are fine.
Comment 6 Jaroslaw Kijanowski 2009-09-16 14:56:34 UTC 
Reopening to change the Fix Version to "future" since tooling patches will not go into the BRMS 5.0.1 release
Note You need to log in before you can comment on or make changes to this bug.