Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SystemConfig Controller does not throw optimistic Lock excepiton if sequenceService updated the doucment #492

Closed
rsoika opened this issue Apr 4, 2022 · 1 comment
Milestone

Comments

@rsoika
Copy link
Member

rsoika commented Apr 4, 2022

Szenarion:

  1. User-A open System config (sequence Number= 1000)
  2. User-B creates a new Workitem (sequence Number= 1001)
  3. User-A saves System config
  4. NOW again sequence Number= 1000 !

A optimisticeLock Exception is expected but did not occure

Solution:

The reason for this behaviour is that the Controller is ApplicationScoped. This means that the VersionID is correctly updated from the internal perspective.

But we need to avoid that in this situaiton the Sequencenumber is overwritten

@rsoika rsoika added the bug label Apr 4, 2022
@rsoika rsoika added this to the 4.5.2 milestone Apr 4, 2022
@rsoika
Copy link
Member Author

rsoika commented Apr 4, 2022

Solution See:
imixs/imixs-marty#380

rsoika added a commit that referenced this issue Apr 4, 2022
Issue #492
rsoika added a commit that referenced this issue Apr 4, 2022
Issue #492
rsoika added a commit that referenced this issue Apr 4, 2022
rsoika added a commit that referenced this issue Apr 5, 2022
Issue #492
@rsoika rsoika added the testing label Apr 19, 2022
@rsoika rsoika closed this as completed Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant