|Re: [XCore] Unable to create a data type of an array of EMF Ecore Classes (e.f. EStructuralFeature) [message #1694320 is a reply to message #1694219]
||Mon, 04 May 2015 12:49
| Ed Merks
Registered: July 2009
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=466305 and
committed the fix. It will be in the M7 build.
On 02/05/2015 3:10 PM, Ed Merks wrote:
> Which version of Xcore are you using?
> On 01/05/2015 5:53 PM, Regent LArcheveque wrote:
>> I would like to model an operation with a parameter that is simple
>> array of EStructuralFeature. But the following line raises an error
>> "type EStructuralFeaturesArray wraps EStructuralFeature"
>> Error Raised: "Couldn't resolve reference to JvmType 'EParameter'"
> I can reproduce this with the Mars version, though the error is about
> EStructuralFeature not EParameter. If I change it to be
> org.eclipse.emf.ecore.EStructuralFeature then the error goes away,
> so it seems yet another scoping problem.
>> Is it possible to do that?
> It should be yes.
>> My meta-model already contains simple reference to EStructuralFeature
>> but the definition of this new Data Type does not seem to work.
> No, from a preliminary analysis, it seems to be a problem that an
> import that can resolve to GenClassifier can't also be used to resolve
> to a JvmType in the cached synthetic import section that's created...
> So there's definitely something that needs to be fixed here. Please
> open a bugzilla. This simple test case reproduces the problem:
> package test
> import org.eclipse.emf.ecore.EStructuralFeature
> type Foo wraps EStructuralFeature
>> Thanks ;)
Powered by FUDForum
. Page generated in 0.02251 seconds