Bug 1031618

Summary: Wrong code completion for query
Product: [Retired] JBoss BRMS Platform 6 Reporter: Tomas Schlosser <tschloss>
Component: Eclipse ToolingAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Tomas David <tdavid>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: mwinkler, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:08:08 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 Tomas Schlosser 2013-11-18 11:59:32 UTC 
Description of problem:
When content assist is invoked in query, it gives wrong possibilities (rule attributes like salience, when, then).

Version-Release number of selected component (if applicable):
JBDS 7.0.1.GA
JBoss Drools Core 6.0.0.201308222359
droolsjbpm-tools 6.x branch (2013-11-18)

Steps to Reproduce:
1. create new DRL resource
2. create a query
3. ask for content assist

Actual results:
[activation-group, agenda-group, auto-focus, date-effective, date-expires, dialect "java", dialect "mvel", duration, enabled, lock-on-active, no-loop, ruleflow-group, salience, when]

Expected results:
Facts that can be used.

Additional info:
Please note that this has been reproduced using query definition offered by content assist earlier i.e.
query "query name"
	#conditions
end

However using brackets after query name (without quotes) with or without parameters, gives expected output.

The fix might be to fix the example query to something like:
query queryName()
	//conditions
end