@rombert could you take into consideration also implementing this - https://issues.apache.org/jira/browse/SLING-4327 ? Still it is unaddressed problem on AEM. Regardless implementation details, now it is not possible to generate on author instance a mapped link pointing to publish instance (when resource resolver mappings root path is different for each run mode).
This case is needed, for example, if project wants to implement content moderation being performed on author which ends with sending e-mail to user-generated content authors informing them that their content has been approved / assuming the link is being a part of that e-mail. That was a real business project scenario and as I remember there was few others, because of that limitation in Sling. Maybe we could do something with that together? Kind regards, Krystian. [ Full content available at: https://github.com/apache/sling-org-apache-sling-api/pull/6 ] This message was relayed via gitbox.apache.org for [email protected]
