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] Updated: (OCM-15) Add more flexibility in the mapping
Date Mon, 27 Apr 2009 15:08:30 GMT

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

Jukka Zitting updated OCM-15:
-----------------------------

    Description: 
Sometime, it should be interesting to map to a different jcr node structure. 
Here is an example, for a class "File", we can have : 

{code}
public class File {

    private String mimeType;

    private String encoding;

    private InputStream data;

    private Calendar lastModified;

    // Add getters/setters
}
{code}

and in terms of JCR structure, we can have : 

{noformat}
nt:file
    jcr:content
        jcr:mimeType
        jcr:encoding
        jcr:data
        jcr:lastModified
{noformat}

So, the jcr:content node is an extra node to specify in the mapping file.




  was:
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.




     Issue Type: Improvement  (was: Bug)

> Add more flexibility in the mapping
> -----------------------------------
>
>                 Key: OCM-15
>                 URL: https://issues.apache.org/jira/browse/OCM-15
>             Project: Jackrabbit OCM
>          Issue Type: Improvement
>            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 : 
> {code}
> public class File {
>     private String mimeType;
>     private String encoding;
>     private InputStream data;
>     private Calendar lastModified;
>     // Add getters/setters
> }
> {code}
> and in terms of JCR structure, we can have : 
> {noformat}
> nt:file
>     jcr:content
>         jcr:mimeType
>         jcr:encoding
>         jcr:data
>         jcr:lastModified
> {noformat}
> 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