jackrabbit-dev mailing list archives

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

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

Alexander Klimetschek commented on JCR-2116:

I see the backwards compatibility issue. Was just inspecting the code that sets those values
if not present.

I think one could auto-set those properties if the mixin is set on the node and a "significant"
modification happened, but if such a value is set via setProperty() no exception is thrown.
Would this be ok wrt the spec?

BTW, in the proposed final draft of JSR-283, the mixin types are defined slightly different
(no question marks anymore and no OPV defined): mix:lastModified 
[mix:lastModified] mixin 
  - jcr:lastModified (date) protected 
  - jcr:lastModifiedBy (string) protected 

> 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