[
https://issues.apache.org/jira/browse/OAK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416078#comment-13416078
]
angela commented on OAK-182:
----------------------------
i am not sure if it wise to expose such invisible content as "regular items" on
the oak-api.
somehow it looks problematic to me that oak-jcr needs to deal with such
internal stuff (and
thus any other implementation of the jcr-api would need to do the same...
wasn't it a valid alternative to really keep that as implementation detail in
oak-core and
just expose the information using specific methods on the oak-api/spi?
> Support for "invisible" internal content
> ----------------------------------------
>
> Key: OAK-182
> URL: https://issues.apache.org/jira/browse/OAK-182
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, jcr
> Reporter: Jukka Zitting
>
> As discussed on the mailing list
> (http://markmail.org/message/kzt7csiz2bd5n3ww), it would be good to have a
> naming pattern line "{{:name}}" for internal content that we don't want to
> directly expose to JCR clients.
> JCR-related functionality like the namespace and node type validators and the
> observation dispatcher (see also OAK-181) should know to ignore such content
> and the JCR binding in oak-jcr should automatically filter out such internal
> content. Such internal content should probably also not be indexed for search.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
