Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [EMFStore] Referenced objects in different projects?
[EMFStore] Referenced objects in different projects? [message #1053712] Tue, 07 May 2013 07:00 Go to next message
Lorenzo Murrocu is currently offline Lorenzo Murrocu
Messages: 1
Registered: December 2011
Junior Member
Hello,
is it possible (or does it make any sense) to have an object with a
eReference (containment false) to an object contained in another
project?

After a request from a customer, I made a little experiment, using the
bowling.ecore:
- I made two different EMFStore projects: prj1 and prj2
- I created a Tournament in prj1 and a Player in prj2
- I made a command that retrieves the tournament and the player
and executes this:
editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));

The result is that the player is correctly added to the tournament, but
it is also moved to prj1. Is there a way to add it without moving it?
Re: [EMFStore] Referenced objects in different projects? [message #1054817 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1054870 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1054923 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1054978 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055033 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055094 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055153 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055214 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055279 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055345 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055410 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055479 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055548 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055618 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055692 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055765 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055843 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055919 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1055998 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056079 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056161 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056245 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056332 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056421 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056513 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056606 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056701 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056798 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056898 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1056998 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057100 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057205 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057309 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057414 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057524 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Re: [EMFStore] Referenced objects in different projects? [message #1057631 is a reply to message #1053712] Wed, 08 May 2013 05:43 Go to previous message
Maximilian Koegel is currently offline Maximilian Koegel
Messages: 118
Registered: July 2009
Senior Member
Hi Lorenzo,

it would make sense to allow cross-project references, but is not yet
supported in EMFStore. It would require some additional thought on
corner cases, e.g. if the other project is not checked out in a client.
Currently EMFStore enforces a self-contained containment tree in a
project therefore. I know that other users have made custom extensions
to allow cross-project references but do not know what exactly they
ended up doing. From my point of view it would also require more
sophisticated URIs to correctly address and resolve EObjects outside of
the current project. Overall it is definitely possible to implement this
with reasonable effort in my opinion.

Cheers,
Maximilian


Am 07.05.2013 13:00, schrieb Lorenzo Murrocu:
> Hello,
> is it possible (or does it make any sense) to have an object with a
> eReference (containment false) to an object contained in another
> project?
>
> After a request from a customer, I made a little experiment, using the
> bowling.ecore:
> - I made two different EMFStore projects: prj1 and prj2
> - I created a Tournament in prj1 and a Player in prj2
> - I made a command that retrieves the tournament and the player
> and executes this:
> editingDomain.getCommandStack().execute(AddCommand.create(editingDomain,
> tournament, BowlingPackage.Literals.TOURNAMENT__PLAYERS, player));
>
> The result is that the player is correctly added to the tournament, but
> it is also moved to prj1. Is there a way to add it without moving it?
>


--
Maximilian Kögel

Get Professional Eclipse Support: http://eclipsesource.com/munich
Previous Topic:Problem with emf2java ant script
Next Topic:[EEF 2.0] How to use the reflective Editor?
Goto Forum:
  


Current Time: Tue May 28 12:13:22 EDT 2013

Powered by FUDForum. Page generated in 0.06574 seconds