Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc)

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Store] A resource lock?

[EMF Store] A resource lock? [message #1063987]

Mon, 17 June 2013 03:22

Eclipse User

Hello,

Is it possible to lock an object / project against other's modifications? I didn't find anything about this functionality.
If it is not implemented yet, do you have any idea how to do it?

Cheers,

Laurent

Re: [EMF Store] A resource lock? [message #1063991 is a reply to message #1063987]

Mon, 17 June 2013 03:49

Eclipse User

Hi Laurent,

no it is currently not possible to do this since it was not yet
implemented.
To implement it, one could use properties on the project to define which
objects are locked. A question in terms of requirements is how to
distribute the locks to offline clients? It could happen that a lock is
established while a client has already checked out a project. Should the
server in this case reject a commit on the locked contents in the project?

Cheers,
Maximilian

Am 17.06.2013 09:22, schrieb Laurent Odermatt:
> Hello,
>
> Is it possible to lock an object / project against other's
> modifications? I didn't find anything about this functionality.
> If it is not implemented yet, do you have any idea how to do it?
>
> Cheers,
>
> Laurent

--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich

Re: [EMF Store] A resource lock? [message #1064014 is a reply to message #1063991]

Mon, 17 June 2013 05:34

Eclipse User

In my mind, it was like this, I don't see any other option but reject the user's
commit.
There are risks of work losses but the only other solution I see now is to send a
message from the server to every other clients to "say" them what objects are locked
when an user lock them... solution which doesn't match the EMF Store philosophy, and
doesn't work with offline clients.

Cheers,

Laurent

[Updated on: Mon, 17 June 2013 05:35] by Moderator

Re: [EMF Store] A resource lock? [message #1064209 is a reply to message #1064014]

Tue, 18 June 2013 05:13

Eclipse User

> In my mind, it was like this, I don't see any other option but reject
> the user's commit. There are risks of work losses but the only other
> solution I see now is to send a message from the server to every other
> clients to "say" them what objects are locked when an user lock them...
> solution which doesn't match the EMF Store philosophy, and doesn't work
> with offline clients.
Seems reasonable to me. Additionally partial commits could be supported
to allow users to commit all changes but changes to the locked objects.

Cheers,
Maximilian

>
> Cheers,
>
> Laurent

--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich

Previous Topic:	Texo authentication and json query
Next Topic:	[Texo] How to know attributes of an object in order to make update/insert requests?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 20:16:20 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter