I know we can add id, css classes and choose the decorator element type, however, my requirement is to add data-attributes to decorator element. is there a way to achieve it?

Hi @akank_23  I have faced the same issue a while ago. In my case, there was a servlet registered on the same resourceType (on page component), the mistake I made was mentioning absolute path(/apps/proj/components/page/...) in the servlet code. Changing it to relative path(proj/components/page/..) h...

Hi, Create a collection variable(ideally a Map with page path as key and content as value) as a global variable at a OSGi service. You can clear the data/cache of Map variable in activate/deactivate method or by registering an activation event or by a servlet with specific parameters either to flush...

We are facing an intermittent issue, OakState conflict, upon user login through SAML. On debugging logs, we found below observations,1. The conflict is of type changeChangedProperty on the property samlResponse at the user node2. At the same time when the OakState conflict occurs we observe another ...

We are facing an intermittent issue, OakState conflict, upon user login through SAML. On debugging logs, we found below observations,1. The conflict is of type changeChangedProperty on the property samlResponse at the user node2. At the same time when the OakState conflict occurs we observe another ...

We are facing an intermittent issue, OakState conflict, upon user login through SAML. On debugging logs, we found below observations,1. The conflict is of type changeChangedProperty on the property samlResponse at the user node2. At the same time when the OakState conflict occurs we observe another ...

We are facing an intermittent issue, OakState conflict, upon user login through SAML. On debugging logs, we found below observations,1. The conflict is of type changeChangedProperty on the property samlResponse at the user node2. At the same time when the OakState conflict occurs we observe another ...

Hi Bhawesh,We faced the same issue earlier, Adobe recommended us to add JVM init argument -Doak.segmentNodeStore.commitFairLock=true and to restart the cq5 service. It reduced the error rate but does not solve the issue completely.