|Add Pacakge imports to the OclParser [message #534917]
||Thu, 20 May 2010 11:34
Originally posted by: philipp.berger.student.hpi.uni-potsdam.de|
I just tried to parse an OCL expression like
....self.oclAsType(MyType1)..., so I got a type not found exception,
which I could fix by giving the full qualified name of the class
This constraint is defined for an EClass in PackageOne, this package has
no references to PackageTwo, but I like to handle subclasses from
PackageTwo in the constraint.
This problem occured while using the org.eclipse.emf.importer.rose for
porting models. In the Rose context all expressions are defined without
full qualified names, but after importing the class visibility seems to
So my question, is it possible to bind severall packages to the
OclParser to avoid full qualified names?