Description of problem: Similarly to bug 983634 that has been ignored, the whole business-central is single-user only. Collaboration does not work. The last user saving an asset of any type wins. If two users edit an asset at the same time, the last commit/save overwrites changes made by the first commit/save. Users are in no way warned that someone else is making changes, there are no conflicts in git. This is not the type of behaviour one would expect of production ready application using git. I'd expect at least a warning. Warning before editing the asset, in the worst case upon saving the changes (optimistic locking). In that case, user shouldn't be allowed to save the changes, because that would overwrite the previous commit. This would still mean the loss of work, but at least the user would notice. If both commits/saves are allowed, then there should be some way to merge them. This would be ideal. Version-Release number of selected component (if applicable): 6.0 ER1
Changes for now are just on master... waiting for Errai team feedback to push it to 0.3.x and 6.0.x branches. https://github.com/droolsjbpm/uberfire/commit/6ca56af11 https://github.com/droolsjbpm/guvnor/commit/5eaf45687 https://github.com/droolsjbpm/kie-wb-common/commit/51047e6df http://github.com/droolsjbpm/drools-wb/commit/3c49d0efa https://github.com/droolsjbpm/jbpm-form-modeler/commit/c582cc18e https://github.com/droolsjbpm/jbpm-designer/commit/cd0331fc2
Changes propagated to 6.0.x and uf 0.3.x: https://github.com/droolsjbpm/uberfire/commit/11d52a7 https://github.com/droolsjbpm/guvnor/commit/5bcae46fc https://github.com/droolsjbpm/kie-wb-common/commit/f393aa77 https://github.com/droolsjbpm/drools-wb/commit/60f0c35bd https://github.com/droolsjbpm/jbpm-form-modeler/commit/f7fb087fad https://github.com/droolsjbpm/jbpm-designer/commit/74440f41f Now every editor needs to be updated (will be executed by other team members).
More changes (to drools-wb): (master) https://github.com/droolsjbpm/drools-wb/commit/4983117df (6.0.x) https://github.com/droolsjbpm/drools-wb/commit/9208509e4 Other editors to follow.
Changes on Form-Modeler Master: https://github.com/droolsjbpm/jbpm-form-modeler/commit/a959b07195f128b39b49f2d1dc3aa0ea5e3a55d5 6.0.x: https://github.com/droolsjbpm/jbpm-form-modeler/commit/f3e8a096122ce3fab501f4129d3af159bc9e0dee
Why is this "POST"? What does that even mean? Is this issue resolved or not?
Porcelli, can you please clarify the status of this issue and if it is done, set it to MODIFIED?
Raising the priority to get it fixed for the product release.
I will definitely be looking into this more, but as of now this issue is not fixed. Consider this blocked by at least bug 1048265. If I find more issues, I will, of course, inform you. As for bug 983634 which is supposedly blocked by this - shouldn't it be the other way? This being blocked by bug 983634?
The global issue has been implemented and solved. As agreed during the release status call, it's marked as modified. There are a few dependent tickets still open should be targeted for 6.0.1 and will be tracked separately.
(In reply to Pedro Zapata from comment #14) > The global issue has been implemented and solved. Issues with the solution were mostly fixed as well - see bugs that block this. Verified with CR2.