Home » Modeling » EMF » [CDO] Issues when trying to import changes from PushTransaction in legacy mode
| [CDO] Issues when trying to import changes from PushTransaction in legacy mode [message #733622] |
Wed, 05 October 2011 08:37  |
|
Hi everyone !
I'm facing issues when trying to import changes stored in a file through
a PushTransaction.
For example, if I create a new element E1 (in Legacy Mode) and set one
of its attribute to VALUE1, save changes locally, close and reopen my
PushTransaction :
in CDOTransactionImpl.importChanges() :
- E1 is created through call to newInstance(revision) ("// Create new
Objects" step)
- E1 is added to its container when applying the revision deltas
("//Apply deltas" step)
- but we never set E1.setMyFeatureValue(VALUE1)
when and how should the last step occur ? Knowing this would help me
debugging and write a CDO testcase repoducing the issue.
Originally I though it was due to SavePoints reconstruction issues, a
bit like https://bugs.eclipse.org/bugs/show_bug.cgi?id=352977 , as we
use a lot savepoints in our software.
But even when I deactivate our SavePoint logic (we set a SavePoint any
time an EMFTransaction is commited, so that rollback of this transaction
correctly reset CDOObjects
in state CLEAN to avoid conflicts, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=352204), I get the same issue.
Thanks by advance for your replies :)
Regards,
Alex
|
|
|
| Re: [CDO] Issues when trying to import changes from PushTransaction in legacy mode [message #733631 is a reply to message #733622] |
Wed, 05 October 2011 08:47  |
|
Hi Alex,
Is it possible that you write a small test case and execute it in the "CDO AllTests (MEM legacy)" launch config?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 05.10.2011 10:37, schrieb Alex Lagarde:
> Hi everyone !
>
> I'm facing issues when trying to import changes stored in a file through a PushTransaction.
>
> For example, if I create a new element E1 (in Legacy Mode) and set one of its attribute to VALUE1, save changes
> locally, close and reopen my PushTransaction :
>
> in CDOTransactionImpl.importChanges() :
> - E1 is created through call to newInstance(revision) ("// Create new Objects" step)
> - E1 is added to its container when applying the revision deltas ("//Apply deltas" step)
> - but we never set E1.setMyFeatureValue(VALUE1)
>
> when and how should the last step occur ? Knowing this would help me debugging and write a CDO testcase repoducing the
> issue.
>
> Originally I though it was due to SavePoints reconstruction issues, a bit like
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=352977 , as we use a lot savepoints in our software.
> But even when I deactivate our SavePoint logic (we set a SavePoint any time an EMFTransaction is commited, so that
> rollback of this transaction correctly reset CDOObjects
> in state CLEAN to avoid conflicts, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=352204), I get the same issue.
>
> Thanks by advance for your replies :)
> Regards,
> Alex
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
| | | |
Goto Forum:
Current Time: Tue Apr 16 04:26:27 GMT 2024
Powered by FUDForum. Page generated in 0.13464 seconds |
] 
Search
Help
Register
Login
Home
