Bug 482144 - Surrogate query for qualified name calculation is still incorrect
Summary: Surrogate query for qualified name calculation is still incorrect
Status: RESOLVED FIXED
Alias: None
Product: Viatra
Classification: Modeling
Component: Query (show other bugs)
Version: oldinquery   Edit
Hardware: All All
: P3 normal
Target Milestone: 1.1 RC   Edit
Assignee: Abel Hegedus CLA
QA Contact: Istvan Rath CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-13 13:01 EST by Zoltan Ujhelyi CLA
Modified: 2015-12-02 12:43 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zoltan Ujhelyi CLA 2015-11-13 13:01:15 EST 
Another issue was found with regards to qualified name calculation for UML.

The problem manifested itself when asking for the qualified name of the primitve type 'PrimitiveTypes::Integer', and the pattern matcher returned four different matches:

 * 'PrimitiveTypes::Integer'
 * 'UML::Integer'
 * 'Ecore::Integer'
 * 'StandardProfile::Integer'

During a (not so short) debug session with Ábel we have found that the most likely culprit is the calculation in the 'namedElementNamespace' pattern, where the inverse of namespaceMember is calculated; however, the namespaceMember pattern also includes elements in imported packages.

We should research the correct way to specify these patterns, and make sure that the qualified name pattern works as intended.
Comment 1 Eclipse Genie CLA 2015-11-29 12:36:59 EST 
New Gerrit change created: https://git.eclipse.org/r/61527
Comment 3 Abel Hegedus CLA 2015-12-02 12:43:19 EST 
The linked Gerrit change improves the surrogate queries for UML considerably and fixes the qualified name issue as well.

For an up to date status of the UML derived features, see https://wiki.eclipse.org/EMFIncQuery/UMLSupport

Bug 483501 is created as a followup issue.