Update: I was able to access the binary package content using below code. Session session = resourceResolver.adaptTo(Session.class);JcrPackageManager jcrPackageManager = packaging.getPackageManager(session);JcrPackage pack = jcrPackageManager.open(new PackageId(path));InputStream binaryStream = pack...

Thanks Lukasz,    That explains the behavior. What options would you recommend for adding the ability to be able to uninstall/revert back in the destination AEM instance? One I can think of is building a package with the same filter/definition on the destination AEM and then replicating from source ...

Hi, I have been using the replication-workflow-process (https://github.com/cqsupport/replication-workflow-process) to trigger a replication from one AEM author instance (source) to another AEM author (destination) via a workflow process step. Everything is working as expected except when attempting ...

Hi,   I'm having an issue with content which is deployed from author and replicated to publisher as a package does not trigger dispatcher cache invalidation. However the same content when activated as an individual asset from author invalidates dispatcher cache immediately after replication to publi...

Thank you for the reply. What you suggest (passing workflow reference along to the replication process) may work. I'm not quite sure how to get that reference from the replication process. The workflow process invokes replication via the following: replicator.replicate(replicationSession, getReplica...

Hi,  I have a custom implementation of a WorkflowProcess (say MyCustomWorkflowProcess), which triggers a custom replication via custom implementation of a TransportHandler (say MyCustomTransportHandler) to trigger CDN cache clear for particular content. All works well however in the event that the r...

Hi, has this feature been implemented? Seems to be working the same way in AEM 6.5 FP 9. Where can I find more information on this feature. I'm looking for a way to collect multiple assets, experience fragments, content fragments and submit as a single workflow instance. Thank you.