Eclipse Community Forums: VIATRA » Use qualified Classifier name

Help

Home

Home » Modeling » VIATRA » Use qualified Classifier name

Show: Today's Messages :: Show Polls :: Message Navigator

Use qualified Classifier name [message #1753785]

Fri, 10 February 2017 08:25

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Hi,

In my .eiq file, I need two import two Ecore packages which contains classifiers having the same name.
In the patterns, I can use only the classifier imported from the first import clause.

I can't find the syntax to be more precise about the classifier, is there a kind of qualified name built with the Ecore package ? Or with the Java generated package ?

An example could be in using the classifiers Constraint, which are present inside Ecore OCL, IQPL and Capella :
import "http://www.eclipse.org/ocl/1.1.0/Ecore"
import "http://www.eclipse.org/incquery/patternlanguage/PatternLanguage"
import "http://www.polarsys.org/capella/core/core/0.8.0"

Cheers,
Eric

Report message to a moderator

Re: Use qualified Classifier name [message #1753793 is a reply to message #1753785]

Fri, 10 February 2017 09:36

Abel Hegedus

Messages: 197
Registered: September 2015

Senior Member

Hi Eric,

depending on your version, you can use the "as" keyword to alias packages. See for example here and used here

import "http://www.eclipse.org/uml2/5.0.0/UML" as uml

pattern typeDefinitionInPackage(umlPackage: Package, type : uml::Type) {
[...]
}

Report message to a moderator

Re: Use qualified Classifier name [message #1753797 is a reply to message #1753793]

Fri, 10 February 2017 10:00

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Thanks Abel,

I read about that, but forgot it as it is not so often needed.

By the way, we're still using IncQuery 0.7 ...
The "as" syntax doesn't seem to be available in this old version ?
Is there another solution ?

Report message to a moderator

Re: Use qualified Classifier name [message #1753798 is a reply to message #1753793]

Fri, 10 February 2017 10:01

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Report message to a moderator

Re: Use qualified Classifier name [message #1753799 is a reply to message #1753793]

Fri, 10 February 2017 10:01

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Report message to a moderator

Re: Use qualified Classifier name [message #1753800 is a reply to message #1753793]

Fri, 10 February 2017 10:02

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Report message to a moderator

Re: Use qualified Classifier name [message #1753801 is a reply to message #1753800]

Fri, 10 February 2017 10:05

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Sorry for duplicates, the thing went crazy ... Please delete as I can't do it myself.

Report message to a moderator

Re: Use qualified Classifier name [message #1753802 is a reply to message #1753800]

Fri, 10 February 2017 10:06

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Sorry for duplicates, the thing went crazy ... Please delete as I can't do it myself.

Report message to a moderator

Re: Use qualified Classifier name [message #1753803 is a reply to message #1753798]

Fri, 10 February 2017 10:12

Abel Hegedus

Messages: 197
Registered: September 2015

Senior Member

I can't remember whether cross-resource find pattern was available in EMF-IncQuery 0.7.0, but if it was, you might be able to workaround the problem by creating three additional EIQ files where each imports only one of the metamodels and create helper patterns for wrapping the individual types, e.g.:

ocl-helper.eiq:

import "http://www.eclipse.org/ocl/1.1.0/Ecore"

pattern oclConstraint(c) {
  Constraint(c);
}

iqpl-helper.eiq:

import "http://www.eclipse.org/incquery/patternlanguage/PatternLanguage"

pattern iqplConstraint(c) {
  Constraint(c);
}

Then you can simply use the helper patterns to enforce the correct type, e.g.

pattern myP() {
  find oclConstraint(c);
  [...]
}

I don't know exactly in which scenarios would the name clash create problems, so this might not work.

Report message to a moderator

Re: Use qualified Classifier name [message #1753942 is a reply to message #1753803]

Mon, 13 February 2017 08:40

Eric Lépicier

Messages: 25
Registered: October 2013

Junior Member

Thanks Abel for this workaround.

Cheers,
--Eric

Report message to a moderator

Previous Topic:	vaitra queries visualised using Sirius
Next Topic:	Importing Ecore metamodel into Modelspace with VIATRA2 R3.1

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 21:32:59 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter