Assume you move a node to position 20 from origin 10. However, in the model server it is not allowed and therefore the node will stay on position 10 - there is no update to the unnotation file -> thus no changes will be sent to the GLSP-Server, and consequently the client will have for the node the invalid position of 20 until it retrieves the whole model again.
Assume you move a node to position 20 from origin 10. However, in the model server it is not allowed and therefore the node will stay on position 10 - there is no update to the
unnotation
file -> thus no changes will be sent to the GLSP-Server, and consequently the client will have for the node the invalid position of 20 until it retrieves the whole model again.Temp Workaround:
com.eclipsesource.uml.modelserver.core.controller.UmlSessionController.commandExecuted(String, Supplier<? extends CCommandExecutionResult>, Supplier<Map<URI, JsonNode>>)
introduced in #149Classes that cause this behavior:
org.eclipse.emfcloud.modelserver.emf.util.JsonPatchHelper.getJsonPatches(EObject, CCommandExecutionResult)
Find a better solution, e.g.:
movement restrictor
)and remove the current workaround