[jira] [Updated] (SLING-5582) DAM Updates fail due to race conditions with Workflows in AEM

["Robert Munteanu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-5582:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.2)
                   Sling Eclipse IDE 1.2.4

> DAM Updates fail due to race conditions with Workflows in AEM
> -------------------------------------------------------------
>
>                 Key: SLING-5582
>                 URL: https://issues.apache.org/jira/browse/SLING-5582
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.10
>            Reporter: Andreas Schaefer
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>
> In my IntelliJ plugin an update of a DAM entry I sometimes run into an exception while updating rendition files. This seems to be caused by the DAM Workflows inside AEM which is triggered as soon as the original file is updated. This is probably due to the fact that the "impl-vlt" code is committing a change after each and every command and so the workflow is triggered right away causing problems with the updates of the rendition files.
> I would think this is not just an issue of DAM assets but in general an issue with any node that can trigger a workflow.
> From my point of view the plugin should be able to control the commits so that a logical group like a DAM asset can be update in single step.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)