Vincent Aranega

Hi @pablo-campillo , Thanks for the report! I tried your use-case, but I cannot reproduce the problem on my side :grimacing:, everything is going just fine... For the execution of...

I'm glad this issue went away :) Regarding the proxies, yes, everytime you deserialize models that are split into different resources, PyEcore puts a proxy to reference the external object....

It should work if the proxy can be resolved meaning if the external resource can be loaded (if it wasn't in the first place), `EClass` and special metaclass redefine `__instancecheck__`...

Unfortunately, PyEcore does not currently support `ExtendedMetaData`, but it is something that is on the roadmap. At the moment, the solution would be to manually rename `nW-PACKAGES` to `nWPACKAGES` in...

Indeed, if you are using the static version of your metamodel, there is a solution. This solution is almost equivalent to the one for derived attributes. In your generated `.py`...

Indeed, with so much attribute, it will be very time consuming. Another solution could be to extend the pyecoregen code generator by adding an extra "task" that would generate the...

@arkumar5 I had some times to check this out, and I wrote a small code generator using pyecoregen/pymultigen which generates equivalent code in a separate file. The code is composed...

Hi @fkgl, Sorry for the late answer, I didn't receive notification. At the moment, there is no way of visualizing a graphical representation of a metamodel using PyEcore. For that,...

I had a little bit of time this morning, so I quickly coded this small script: https://gist.github.com/aranega/eca9c8fbbd87b2f9c70317da53676ac6 You can use it this way ```bash python plantumlgen.py mymetamodel.ecore ``` It will...

Hi @hebin123456 , Sorry for the late answer! I played a little bit with your metamodels and it turns out that one of your metamodel as a class hierarchy that...