[
https://issues.apache.org/jira/browse/SLING-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184918#comment-15184918
]
Robert Munteanu commented on SLING-5582:
----------------------------------------
Ah, I see why this can be problematic and now I understand your suggestion.
Can you replicate the error in Eclipse if you publish a whole sub-tree? See
https://sling.apache.org/documentation/development/ide-tooling.html#manual-content-sync
for instructions.
> 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
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> 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
(v6.3.4#6332)
