jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-182) Support for "invisible" internal content
Date Tue, 24 Jul 2012 10:56:33 GMT

    [ https://issues.apache.org/jira/browse/OAK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421322#comment-13421322
] 

Thomas Mueller commented on OAK-182:
------------------------------------

> I think the ValidatingEditor shouldn't ignore hidden content... the MergingNodeStateDiff
class probably shouldn't ignore hidden content.

For index content, I don't agree. I see no reason to validate or merge changes in the index.
The only hidden content I aware of is index content.

But the tests seem to work now, so I will not change add the filtering to ValidatingEditor
and MergingNodeStateDiff. I guess we will come back to this once it's a performance problem.

Also, I will change NodeStateUtils.isHidden() to support simple names only.


                
> 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
>         Attachments: OAK-182-b.patch
>
>
> 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

        

Mime
View raw message