[
https://issues.apache.org/jira/browse/SLING-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484158#comment-14484158
]
Alexander Klimetschek commented on SLING-4579:
----------------------------------------------
Why does it need to be independent from JCR? If there is need, let's decouple
the generic part from the JCR resource provider, but all this reinventing the
wheel...
The current change misses the check for a {{sling:Message}} node type (which
must respect inheritance since often the {{sling:MessageEntry}} "main" node
type).
> Regression introduced by SLING-4512 : JCR API used in i18n implementation
> -------------------------------------------------------------------------
>
> Key: SLING-4579
> URL: https://issues.apache.org/jira/browse/SLING-4579
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: i18n 2.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Critical
> Fix For: i18n 2.4.2
>
>
> The i18n module should be free from JCR API usage to allow it to run on any
> resources providing i18n messages. SLING-4512 unfortunately removed this
> functionality by directly using JCR API
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
