Hi everyone!
To put you in context I've got this page, let's call it List Page, with several components of the same type, let's call these components Task Component (it's a regular AEM component).
So the List page have a lot of Task components, when I replicate the List page from Author to Publish I need to detect on Publish which tasks were deleted or added in comparison with the previous state of the page before the replication.
I have set up a replication listener but the ReplicationActionType.ACTIVATE or ReplicationActionType.DELETED is only triggered related to the page, so I only get the event in relation with the List page instead of the task components.
Is there a way to detect this subnodes (task components) getting deleted or added in the replication listener?
Thank you!
Solved! Go to Solution.
Views
Replies
Total Likes
You would need to add your own APP logic to perform this. Maybe even code it to create a XML or JSON schema and then compare that on each rep event. That way - you can track the node activity and know which ones are new and which ones are removed. But this would all be custom - which is the point of the various AEM APIS - to enable developers to build such custom functionality.
Views
Replies
Total Likes
"Is there a way to detect this subnodes (task components) getting deleted or added in the replication listener?"
When you say Sub nodes - I assume that you are referring to the the sub nodes to the page - which are the components. For example:
By default - a rep event listener is not aware what happens at this level. You would need to write custom Java logic to track which components are part of the page and which ones have been removed. You could use JCR API to perform this level of node app logic.
Views
Replies
Total Likes
Exactly that's what I mean with sub nodes. So there is nothing already built to track this?
Views
Replies
Total Likes
You would need to add your own APP logic to perform this. Maybe even code it to create a XML or JSON schema and then compare that on each rep event. That way - you can track the node activity and know which ones are new and which ones are removed. But this would all be custom - which is the point of the various AEM APIS - to enable developers to build such custom functionality.
Views
Replies
Total Likes
Views
Likes
Replies