HiWanted to share my experience and learning with the group. I have faced same issues with maven-compiler and scr annotations with JDK 1.8 and AEM 6.1. I eventually found that its a maven compiler and related dependencies' compatibility to JDK 1.8 issue and resolved with following changes in my reac...

Got this working. Wanted to respond to the group earlier..but here is what I did:1) Follow the instruction and create a JSONPStore2) Put following code in the component JSP / script to read the store properties and do content targeting -- <script language="javascript">    CQ.Ext.onLoad(function() { ...

Unfortunately, it has not yet been replicated in DEV. We are doing following:1) Looking at external data that get ingested and check the oak-indexes to ensure whether all content types /  properties are covered2) We are also monitoring all queries and its responsesI guess Adobe would need these info...

Of total repo size of 30 gig, a 3%-4% change through nightly job ingestion causes the authoring to do indexing of content for hours (almost better part of the day. This points to some inconsistencies in either indexes or mechanism of indexing. This is not the behavior if we create a bulk of editoria...

Is there a way to get client context data in AEM component (instead of segments)...appreciate any help in this regard

Thanks Orotas. Option#2 seems more favorable for the requirement. Agreed with you that #1 is highly unreliable. Long path dig in for CQ libraries.... Thanks for your response. Anand

@Sam205505050....thanks for your response. I believe this would be helpful for me to trigger a specific replication agent however I still have to customize Transport library to create nodes at two locations one of which (one path out of two replicated paths at CQ publisher) does not exist in author....