You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/04/25 10:57:18 UTC
[jira] Moved: (JCR-877) Add more flexibility in the mapping
[ https://issues.apache.org/jira/browse/JCR-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting moved GRFT-54 to JCR-877:
---------------------------------------
Fix Version/s: (was: 1.0-a1-dev)
Component/s: (was: JCR-Mapping)
jcr-mapping
Affects Version/s: (was: 1.0-a1-dev)
Key: JCR-877 (was: GRFT-54)
Project: Jackrabbit (was: Graffito)
> Add more flexibility in the mapping
> -----------------------------------
>
> Key: JCR-877
> URL: https://issues.apache.org/jira/browse/JCR-877
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jcr-mapping
> 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.