jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Moved: (OCM-15) Add more flexibility in the mapping
Date Mon, 27 Apr 2009 15:02:36 GMT

     [ https://issues.apache.org/jira/browse/OCM-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting moved JCR-877 to OCM-15:
--------------------------------------

    Component/s:     (was: jackrabbit-ocm)
     Issue Type: Bug  (was: Improvement)
       Workflow: no-reopen-closed, patch-avail  (was: jira)
            Key: OCM-15  (was: JCR-877)
        Project: Jackrabbit OCM  (was: Jackrabbit Content Repository)

> Add more flexibility in the mapping
> -----------------------------------
>
>                 Key: OCM-15
>                 URL: https://issues.apache.org/jira/browse/OCM-15
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            Reporter: Christophe Lombart
>
> Sometime, it should be interesting to map to a different jcr node structure. 
> Here is an example, for a class "File", we can have : 
> public class File
> {
>     private String mimeType;
>     private String encoding;
>     private InputStream data;
>     private Calendar lastModified;
>     // Add getters/setters
> }
> and in terms of JCR structure, we can have : 
> nt:file
>     jcr:content
>         jcr:mimeType
>         jcr:encoding
>         jcr:data
>         jcr:lastModified
> So, the jcr:content node is an extra node to specify in the mapping file.

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


Mime
View raw message