Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » dynamic_package loading metamodels(loading a .ecore with extension point dynamic_package, but still is cannot be used in the platform)
dynamic_package loading metamodels [message #502445] Tue, 08 December 2009 10:04 Go to next message
Simon is currently offline SimonFriend
Messages: 13
Registered: October 2009
Junior Member
Hello Community,

I created 3 .ecore files and tried to load them with the extension point dynamic_package of org.eclipse.emf.ecore.
It looks like:

    <extension
         point="org.eclipse.emf.ecore.dynamic_package">
      <resource
            location="models/MDPE-Core-New.ecore"
            uri="http://www.modelplex.org/amf/2008/MDPE/Core-New">
      </resource>
      <resource
            location="models/MDBPE-Company-Core.ecore"
            uri="http://www.modelplex/amf/2008/MDBPE/Company/Core">
      </resource>
      <resource
            location="models/MDBPE-Department-Core.ecore"
            uri="http://www.modelplex/amf/2008/MDBPE/Department/Core">
      </resource>      
   </extension>


After starting a new Runtime-Configuration I find the package registered, when I check it for instance in the Metamodel Explorer. But when I try to load a model, which uses these metamodels, then Eclipse cannot find the used elements of the metamodel.
Also when I try to create in the runtime configuration a new metamodel which should extend one of the registered metamodels, I cannot load one of these through "Load Resource", only possible loading as "Runtime Version" and not as "Development Time Version". By the way what are the difference between these to versions?

Any ideas I would appreciate.
Simon
Re: dynamic_package loading metamodels [message #502488 is a reply to message #502445] Tue, 08 December 2009 14:18 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30653
Registered: July 2009
Senior Member
Simon,

Comments below.

Simon wrote:
> Hello Community,
>
> I created 3 .ecore files and tried to load them with the extension
> point dynamic_package of org.eclipse.emf.ecore.
> It looks like:
>
>
> <extension
> point="org.eclipse.emf.ecore.dynamic_package">
> <resource
> location="models/MDPE-Core-New.ecore"
> uri="http://www.modelplex.org/amf/2008/MDPE/Core-New">
> </resource>
> <resource
> location="models/MDBPE-Company-Core.ecore"
> uri="http://www.modelplex/amf/2008/MDBPE/Company/Core">
> </resource>
> <resource
> location="models/MDBPE-Department-Core.ecore"
> uri="http://www.modelplex/amf/2008/MDBPE/Department/Core">
> </resource> </extension>
>
>
> After starting a new Runtime-Configuration I find the package
> registered, when I check it for instance in the Metamodel Explorer.
> But when I try to load a model, which uses these metamodels, then
> Eclipse cannot find the used elements of the metamodel.
The should appear in the EPackage.Registry.INSTANCE just like a
registered generated package and should be found just as any other. I'm
not sure why that sound't be the case for you.
> Also when I try to create in the runtime configuration a new metamodel
> which should extend one of the registered metamodels, I cannot load
> one of these through "Load Resource", only possible loading as
> "Runtime Version" and not as "Development Time Version". By the way
> what are the difference between these to versions?
Given there is no GenModel for these, there is no development time
version. The development time version is always a dynamic one, but it's
not registered because the generated one is registered instead; it's
wrapped by a GenModel and available in that way.
>
> Any ideas I would appreciate.
> Simon
Previous Topic:[TENEO & GMF] Copy/Paste not working with Semantic Model in Teneo
Next Topic:eIsSet and multiple inheritance
Goto Forum:
  


Current Time: Fri Nov 22 06:01:17 GMT 2019

Powered by FUDForum. Page generated in 1.89799 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top