incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christophe Lombart <christophe.lomb...@gmail.com>
Subject Re: [jira] Created: (GRFT-37) Final JCR Mapping Document PROPOSAL
Date Sun, 28 Aug 2005 08:35:19 GMT
2005/8/27, Sandro Böhme <sandro.boehme@gmx.de>:
> Oliver Kiessler wrote:
> 
> >> >Here is a simplification of the Sandro proposal....
> >>I'm more for a mapping file similar to this:
> >>        <mapping>
> >>            <classAttributes
> >>packageName="org.apache.portals.graffito.jcr.testmodel"
> >>className="CmsObject"/>
> >>            <nodeTypeAttributes nodeTypeName="graffito:CmsObject">
> >>                <supertype>nt:base</supertype>
> >>            </nodeTypeAttributes>
> >>            <subitemMapping propertyName="objectId" parameterType="long"
> >>jcrPropertyDefinition name="graffito:parentId" />
> >>       </mapping>
> >>
> >>
> >
> >Just to clarify things: We have two types of mapping files, one for
> >the node type registration (bean to jcr custom node type mapping) and
> >one for the actual persistence mapping of beans to jcr nodes. correct?
> >
> >

What is not possible to create jcr node type with my proposal ? With
this file and the java instrospection API, I have all infor to
register node type. but maybe I'm wrong ?

Maybe we can adde moree detail on that topic in our document proposal. 
Is it make sense for you if we register node types like this : 
* Register jcr node type should be an external tools that can be used
by other projects. This tools can be executed from ant, maven or a
more advanced tools (see what Oliver is doing in the Karma project).
* Since the node type management is out of the current JCR spec. We
need to create a set of tools (at least one for JackRabbit) . This
tools can call the appropriate jackrabbit  API
* We can register node type with an xml file that looks like the
"custom_nodetyes.xml".
* In our case, we have 2 steps to register node type : 



> 
> >Because I think Sandro is refering to the node type registration
> >mapping file and Christophe is refering to the beans to jcr nodes
> >mapping file.
> >
> >One comment to the jcr-mapping proposal textfile:
> >
> >2.2 The mapping file
> >I would like to suggest to make field descriptors simpler:
> >
> ><field-descriptor fieldName="a1" jcrName="a1" />
> >to
> ><field-descriptor fieldName="a1" />
> >
> >If "jcrName" is not specified the same name as the "fieldName" is
> >used. I would suggest to make "jcrName" optional.
> >
> >
> In my opinion it should be possible to get all information for the node
> type registration and later
> for the class creation out of one mapping file.
> 
> >@Christophe: Please let me know where I can join in and help coding.
> >
> >regards,
> >oliver
> >
> >
> >
> >
> Regards,
> 
> Sandro
> 
>

Mime
View raw message