topic Re: Calling a validator once per change in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/calling-a-validator-once-per-change/m-p/119922#M84534 <HTML><HEAD></HEAD><BODY><SPAN>Alright, so I'm looking into the DomainModelChangeListener that is registered on the Editor. It is called on every change, which is nice. But I noticed that the BPMN model of Activiti is not updated when the user uses the undo and redo logic. Is that supposed to be like that? 'Cause I think this affects all validators and marshallers that are getting the diagram and work on the flow elements.</SPAN><BR /><BR /><SPAN>Just tested if the export/save to xml is affected by it and it is. If you delete an element, return it via an undo and then save the diagram, that element is not included.</SPAN><BR /><BR /><SPAN>My workaround for that is that I disabled the undo and redo commands of Graphiti by overwriting the initializeActionRegistry method in the ActivitiDiagramEditor to do nothing. Copy, paste, delete via DEL and multiple selection still works with that.</SPAN></BODY></HTML> Mon, 13 May 2013 11:06:20 GMT norberts 2013-05-13T11:06:20Z Calling a validator once per change https://connect.hyland.com/t5/alfresco-archive/calling-a-validator-once-per-change/m-p/119921#M84533 Hey,so I wrote my own validator and since the extension point is deactivated right now I call it in the doSave method ActivitiDiagramEditor for testing purposes. However I want to call it now whenever a change occurs in the diagram of the editor. So every time the user moves/adds/deletes elements an Mon, 06 May 2013 13:48:40 GMT https://connect.hyland.com/t5/alfresco-archive/calling-a-validator-once-per-change/m-p/119921#M84533 norberts 2013-05-06T13:48:40Z Re: Calling a validator once per change https://connect.hyland.com/t5/alfresco-archive/calling-a-validator-once-per-change/m-p/119922#M84534 <HTML><HEAD></HEAD><BODY><SPAN>Alright, so I'm looking into the DomainModelChangeListener that is registered on the Editor. It is called on every change, which is nice. But I noticed that the BPMN model of Activiti is not updated when the user uses the undo and redo logic. Is that supposed to be like that? 'Cause I think this affects all validators and marshallers that are getting the diagram and work on the flow elements.</SPAN><BR /><BR /><SPAN>Just tested if the export/save to xml is affected by it and it is. If you delete an element, return it via an undo and then save the diagram, that element is not included.</SPAN><BR /><BR /><SPAN>My workaround for that is that I disabled the undo and redo commands of Graphiti by overwriting the initializeActionRegistry method in the ActivitiDiagramEditor to do nothing. Copy, paste, delete via DEL and multiple selection still works with that.</SPAN></BODY></HTML> Mon, 13 May 2013 11:06:20 GMT https://connect.hyland.com/t5/alfresco-archive/calling-a-validator-once-per-change/m-p/119922#M84534 norberts 2013-05-13T11:06:20Z