Thanks, arunp99088702​. Yes, correct. The challenge however is the link provided in the workflow step (payload). If you work on an AEM Content Fragment and want to review the content fragment via workflow, then the payload link does not show the content fragment. It actually does nothing...I could o...

Yes, the link shows how to create an AEM Content Fragment. However, how do you review the content fragment in a workflow step? The payload has the link to the content fragment and will never have a link to another page containing the fragment.It's similar to an asset in the workflow step: clicking o...

In AEM 6.2 I created a simple workflow model with only participation steps. This is for reviewing/approving/publishing AEM Content Fragments.I tried two options, but one doesn't work and the other seems to have an error...I created a workflow launcher that listens to the AEM Content Fragment section...

Another observation:If the folder exists in Assets, replication of that folder does nothingIf the folder is new and has not been replicated yet, the replication process only replicates the folder, not it's content.This is an indication that the "Publish" feature within the context menu of a folder i...

I am noticing an interesting issue and am not sure if it's a bug or some configuration is missing. When selecting a folder in Assets and then select "Publish" from the context menu, no replication happens:Use the AEM Content Fragment tool to create a new folder (it's in the DAM) and a new content fr...

To summarize:Don't get confused with the deprecation of the Apache Sling JSON implementation. This was due to licensing issues.The org.json library is used in the CSRF servlet, and (not sure though) seems to not be wrapped.You can test if you have an org.json library overload issue with http://local...

Thanks, Scott and once I have their answer, we can either recommend not to use org.json or do a write-up how to use org.json properly.

Yes, Apache encountered licensing issues with the standard org.json libraries and deprecated their "light JSON" implementation org.apache.commons.json. However, in this case the issue is that (according to the error message) the CSRF servlet seems to use the standard org.json libraries and if we use...

Yes, but at the moment it seems more like defining a workaround for a major issue. Perhaps there is something I am missing like e.g. a statement somewhere saying I should not use org.json or so.The weird thing is that removing the dependency on org.json fixed the problem. But it also fixed other Tou...

And once again I am answering my own question...Let me summarize:If you add a dependency for org.json, similar to this:<dependency>  <groupId>org.json</groupId>  <artifactId>json</artifactId>  <version>20170516</version></dependency>You will trigger the error 02.12.2017 10:32:37.131 *ERROR* [0:0:0:0...