incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandro Böhme <sandro.boe...@gmx.de>
Subject Re: [jira] Created: (GRFT-37) Final JCR Mapping Document PROPOSAL
Date Sun, 28 Aug 2005 12:25:47 GMT
Christophe Lombart wrote:

 >Here is a simplification of the Sandro proposal....

>What is not possible to create jcr node type with my proposal ? With
>  
>
Right, that's _your_ proposal.

>this file and the java instrospection API, I have all infor to
>register node type. but maybe I'm wrong ?
>  
>
I think you are right.

>Maybe we can adde more 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 (or the API proposed by
>the JCR server).
>* We can register node type with an xml file that looks like the
>"custom_nodetyes.xml" (see the Jackrabbit project).
>* In our case, we have 2 steps to register node type :
>- Create a custom_nodetypes.xml from ou mapping file (and the Java
>introspection).
>- Use the appropriate tools to import them into the jcr server
>
>  
>
+1 for the whole statement

I suggest to use different mail-threads for different aspects of the 
proposal because in the
other case this thread will grow quite fast like the "An initial code 
base for the mapping
project."-thread. It will make a more clear documentation of the 
arguments. We can
put the results in the final architecture document.

Regards,

Sandro




Mime
View raw message