You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2012/07/13 10:20:34 UTC
[jira] [Commented] (OAK-182) Support for "invisible" internal
content
[ https://issues.apache.org/jira/browse/OAK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413580#comment-13413580 ]
Thomas Mueller commented on OAK-182:
------------------------------------
> Such internal content should probably also not be indexed for search.
That's certainly possible. Later on we can still allow indexing such 'hidden' properties once we have a use case.
> 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