jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2116) JSR 283: Built-In Node Types
Date Tue, 28 Jul 2009 21:36:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736318#action_12736318

Tobias Bocanegra commented on JCR-2116:

please note, that jcr:lastModified(by) is currently not defined protected in jackrabbit for
ensuring backwards compatibility. this is according to the spec that defines the protected
attribute as variant: 
[mix:lastModified] mixin 
  - jcr:lastModified (DATE) protected? OPV? 
  - jcr:lastModifiedBy (STRING) protected? OPV? 

This mixin node type can be used to provide standardized modification 
information properties to a node. Since the properties are protected, their values 
are controlled by the repository, which should set them appropriately upon a 
significant modification of the subgraph of a node with this mixin. What 
constitutes a significant modification will depend on the semantics of the various 
parts of a node's subgraph and is implementation-dependent. 

however, i will look into the jcr:created issue

> JSR 283: Built-In Node Types
> ----------------------------
>                 Key: JCR-2116
>                 URL: https://issues.apache.org/jira/browse/JCR-2116
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>          Components: jackrabbit-core, nodetype
>            Reporter: Stefan Guggisberg
>            Assignee: Tobias Bocanegra
>             Fix For: 2.0.0
> sync definitions of built-in node types with spec

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message