Bug 1031618 - Wrong code completion for query
Wrong code completion for query
Status: ASSIGNED
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Eclipse Tooling (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Kris Verlaenen
Tomas David
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-18 06:59 EST by Tomas Schlosser
Modified: 2016-01-08 17:21 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Schlosser 2013-11-18 06:59:32 EST
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

Note You need to log in before you can comment on or make changes to this bug.