|
|
|
Re: EMF Transaction advice needed [message #381194 is a reply to message #381193] |
Mon, 20 August 2007 15:38 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: cdamus.ca.ibm.com
Hi, Marko,
If your projects are truly independent, then it is probably best these
editors use separate editing domains. This ensures that there can be no
"cross-talk" in the contents of your resources, and allows the different
editors to work concurrently in their separate domains without contending
for unnecessary locks.
Of course, if your requirements should change and you find that the
resources from multiple projects need to be edited together because they
cross-reference one another, it is easy to change your editor to share a
single editing domain (using the editing domain registry).
The EMF metadata isn't really such an issue, as it is largely static
(generated to Java code) and thus isn't owned in the context of any
resource set. Unless, of course, you are using dynamic EMF or importing
schema from XSD on the fly ... then you possibly do want separate instances
of the schema in each resource set, and in each project.
HTH,
Christian
Marko T. wrote:
> Sorry about the wrong newsgroup. I will use the right one in future posts.
>
> Now, about the projects.
>
> Each project will be independent of the others regarding the editor
> instances but several projects will contain files with the same emf meta
> model that will be edited by the editor instances.
|
|
|
Re: EMF Transaction advice needed [message #599284 is a reply to message #381191] |
Mon, 20 August 2007 10:59 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Ed Merks![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=ed.merks%40gmail.com) Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
Marko,
Please use the EMF newsgroup for questions about transactions. I've
added it to the "to" list of the reply. Are the instances in the
separate projects related in some way, or are they completely independent?
Marko T. wrote:
> Hello guys,
> since EMFT moved to the EMF project I am posting the question here.
>
> I am just going through the EMFT examples dled from the EMF website. I
> have played a bit with the example workspace editor and I am having
> some doubts about my understanding of EMFT. Thats why I need some advice.
>
> I am planing to write an editor plugin that should use transactions to
> perform the read and write actions. Per project multiple editor
> instances of the same kind will be opened. There will be multiple
> projects open simultaneously.
>
> The thing is that I do not know how to handle the EditingDomain
> instances. Should I only use one for all instances of the editor (but
> then I would mixup the resources of different projects). Or is it
> better to only use one Editing Domain for one project or one for
> everything?
>
> Greetings Marko T.
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Re: EMF Transaction advice needed [message #599306 is a reply to message #381193] |
Mon, 20 August 2007 15:38 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: cdamus.ca.ibm.com
Hi, Marko,
If your projects are truly independent, then it is probably best these
editors use separate editing domains. This ensures that there can be no
"cross-talk" in the contents of your resources, and allows the different
editors to work concurrently in their separate domains without contending
for unnecessary locks.
Of course, if your requirements should change and you find that the
resources from multiple projects need to be edited together because they
cross-reference one another, it is easy to change your editor to share a
single editing domain (using the editing domain registry).
The EMF metadata isn't really such an issue, as it is largely static
(generated to Java code) and thus isn't owned in the context of any
resource set. Unless, of course, you are using dynamic EMF or importing
schema from XSD on the fly ... then you possibly do want separate instances
of the schema in each resource set, and in each project.
HTH,
Christian
Marko T. wrote:
> Sorry about the wrong newsgroup. I will use the right one in future posts.
>
> Now, about the projects.
>
> Each project will be independent of the others regarding the editor
> instances but several projects will contain files with the same emf meta
> model that will be edited by the editor instances.
|
|
|
Powered by
FUDForum. Page generated in 0.04357 seconds