Eclipse Community Forums: EMF » Loading ecore as dynamic instances from a workspace

Home » Modeling » EMF » Loading ecore as dynamic instances from a workspace

Loading ecore as dynamic instances from a workspace [message #1066422]

Tue, 02 July 2013 11:28

Eclipse User

Hi there,

here are some questions:

1)

Scenario:

* a core engineer is working on a standard ecore (f.e. standard.ecore)
* this ecore will be registered using the 'org.eclipse.emf.ecore.dynamic_package' in a bundle 'standard.bundle'
* the 'standard.bundle' will be provided to other engineers which can make use of this 'standard.ecore' while referring to it in their extension ecores.

This works fine as long as the 'standard.ecore' is used within a target platform. The core engineers however would like to make their changes to the 'standard.ecore' while editing extension ecore in the same workspaces as well.

So here's my question: Is there something like an action which allows to register/reload an ecore or is there any alternative solution ?

2)

Scenario:

* the 'Sample Ecore Editor' always inserts the platform resource location of a referred ecore.

Is there a way to enforce the usage of the namespace URI of the referred ecore ?

Thanks in advance

Re: Loading ecore as dynamic instances from a workspace [message #1066436 is a reply to message #1066422]

Tue, 02 July 2013 12:01

Eclipse User

Daniel,

Comments below.

On 02/07/2013 5:28 PM, Daniel Kasmeroglu wrote:
> Hi there,
>
> here are some questions:
>
> 1)
>
> Scenario:
>
> * a core engineer is working on a standard ecore (f.e. standard.ecore)
> * this ecore will be registered using the
> 'org.eclipse.emf.ecore.dynamic_package' in a bundle 'standard.bundle'
> * the 'standard.bundle' will be provided to other engineers which can
> make use of this 'standard.ecore' while referring to it in their
> extension ecores.
>
> This works fine as long as the 'standard.ecore' is used within a
> target platform. The core engineers however would like to make their
> changes to the 'standard.ecore' while editing extension ecore in the
> same workspaces as well.
>
> So here's my question: Is there something like an action which allows
> to register/reload an ecore or is there any alternative solution ?
The package instances in the registry should never be changed. They
don't need to be in the registry if you want to be able to change them.
Then each client can load their own copy (perhaps from a serialization
packaged in the bundle) and edit it as they see fit.
>
>
> 2)
>
> Scenario:
>
> * the 'Sample Ecore Editor' always inserts the platform resource
> location of a referred ecore.
>
> Is there a way to enforce the usage of the namespace URI of the
> referred ecore ?
Always the URI of the resources will be used, so you can make those URIs
be whatever you want. Generally any root package in the registry will
be contained by a resource whose URI's string is equal to the nsURI.
>
>
> Thanks in advance
>
>

Previous Topic:	[EMF/CDO] instanceof EObject/Resource issue
Next Topic:	Is there a headless feature fur running MWE2 workflows?

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 13 02:09:16 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter