Description of problem: When saving changes made to a project for the second time, user gets Conflict Error modal: "User has updated the following resource default://master@<repo>/<project>/pom.xml." 1st and main issue is that only this one user was making the changes and so there is no conflict. 2nd issue is that the Conflict Error modal message doesn't specify which user has made the changes. Version-Release number of selected component (if applicable): BPMS 6.0.2 ER1 Steps to Reproduce: 1. Open the Project Editor. 2. Change project version and save. 3. repeat step 2. Actual results: Error modal warning about a conflict. Expected results: Changes are saved, no conflict. (In case of actual conflict, the message informs which user has made the changes as well.)
Looks like the patch commit, that is used to commit all the files Project Editor edits, does not use the same session ID as the current session. The id there is "<system>" instead of a generated hash. If the session ID's do not match, then the we fire a concurrent edit event that causes this message. I'm pretty sure this is a bug in UF. Going to take a look at it next.
I can verify Toni's investigations. A VFS "batch" operation is not setting the SessionId in the WatchContext so a default of "<system>" is being used which causes the client-side optimistic concurrent lock mechanism to incorrectly report the file has been saved by another user. Batches of 1 or more changes are affected. Would you mind taking a look?
Fix pushed to uberfire: (master) http://github.com/uberfire/uberfire/commit/c889ea053