You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2012/11/28 18:30:57 UTC

[jira] [Created] (SLING-2687) JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes

Alexander Klimetschek created SLING-2687:
--------------------------------------------

             Summary: JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes
                 Key: SLING-2687
                 URL: https://issues.apache.org/jira/browse/SLING-2687
             Project: Sling
          Issue Type: Improvement
          Components: JCR
    Affects Versions: JCR Resource 2.2.0
            Reporter: Alexander Klimetschek
            Priority: Minor


JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types.

I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
* look at "jcr:content" for all nt:hierarchyNodes (or maybe all nodes that have a "jcr:content" child
* look at current node first, if property not found there, take from "jcr:content"
* the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2687) JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes

Posted by "Alexander Klimetschek (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek updated SLING-2687:
-----------------------------------------

    Description: 
JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types that commonly store all their metadata inside the "jcr:content".

I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
* look at "jcr:content" for all nt:hierarchyNodes (or maybe all nodes that have a "jcr:content" child
* look at current node first, if property not found there, take from "jcr:content"
* the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

  was:
JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types.

I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
* look at "jcr:content" for all nt:hierarchyNodes (or maybe all nodes that have a "jcr:content" child
* look at current node first, if property not found there, take from "jcr:content"
* the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

    
> JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-2687
>                 URL: https://issues.apache.org/jira/browse/SLING-2687
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Resource 2.2.0
>            Reporter: Alexander Klimetschek
>            Priority: Minor
>
> JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types that commonly store all their metadata inside the "jcr:content".
> I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
> * look at "jcr:content" for all nt:hierarchyNodes (or maybe all nodes that have a "jcr:content" child
> * look at current node first, if property not found there, take from "jcr:content"
> * the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2687) JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes

Posted by "Alexander Klimetschek (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Klimetschek updated SLING-2687:
-----------------------------------------

    Description: 
JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types that commonly store all their metadata inside the "jcr:content".

I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
* look at "jcr:content" for all nt:hierarchyNodes
* or maybe all nodes that have a "jcr:content" child
* look at current node first, if property not found there, take from "jcr:content"
* the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

  was:
JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types that commonly store all their metadata inside the "jcr:content".

I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
* look at "jcr:content" for all nt:hierarchyNodes (or maybe all nodes that have a "jcr:content" child
* look at current node first, if property not found there, take from "jcr:content"
* the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

    
> JcrNodeResource.setMetaData(): take metadata from jcr:content for nt:hierarchyNodes
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-2687
>                 URL: https://issues.apache.org/jira/browse/SLING-2687
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Resource 2.2.0
>            Reporter: Alexander Klimetschek
>            Priority: Minor
>
> JcrNodeResource.setMetaData() currently only takes a "jcr:content" child node into account for nt:file nodes (and then only uses it, but not the resource node itself). This makes the use of the generic ResourceMetadata quite restricted, and you have to resort to the JCR API again when handling other nt:hierarchyNode types that commonly store all their metadata inside the "jcr:content".
> I suggest that for the time stamp properties "jcr:lastModified" and "jcr:created":
> * look at "jcr:content" for all nt:hierarchyNodes
> * or maybe all nodes that have a "jcr:content" child
> * look at current node first, if property not found there, take from "jcr:content"
> * the "jcr:data", "jcr:mimeType" and "jcr:encoding" properties should continue to be taken from "jcr:content" and only if this is a nt:file (or generalize: the "jcr:content" child node is a nt:resource?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira