[Cps4] cps/jcr document mapping

[Eric Barroca]

Hi,

On 7 avr. 06, at 16:25, Florent Guillaume wrote:
>> We need to manage it with childnodes (like node type  
>> cps:contentfragment).
> Ok so basically they'll be like small special subdocuments. JCR can  
> do that well, they're just subnodes.
It's not like subdocuments (for me a subdocument is like a Question/ 
Answer for a FAQ).
I also have a need for small subdocuments, but it's different. The  
need is to manage data block of the same document.
In fact it's really like a complexType that would be use as part as  
the main document.

>> In fact, it's the exact use case of supporting XSD ComplexTypes.
>> For schemas management, are we still considering to use XSD? I  
>> think this approach need ot be kept.
> The schema will be defined by the introspection of the node types  
> in the JCR at startup. We can convert that to XSD if needed.
> But we'll need an internal python representation for them, more  
> complex than the existing CPS Schemas which are a list of fields.
> I expect we'll end up with a new schemas tool that will be quite  
> different.
Well why not do XSD -> Python Representation on CPS side and XSD ->  
NodeTypeDef in JCR.
Or just XSD -> NodeTypeDef in JackRabbit and then get the Python  
representation from the JCR node types's def.

I really like the XSD approach because we *need* to be able to create  
new content type in 2 weeks at max.


A+

EB.

--
Éric Barroca - Tel: +33 6 21 74 77 64 (mobile).
Nuxeo - Open Source ECM - www.nuxeo.com
CPS Platform - The open source ECM Platform
http://cps-project.org - http://www.nuxeo.com/en/cps



-------------- next part --------------
An HTML attachment was scrubbed...
URL: /cgi-bin/mailman/private/cps4/attachments/20060407/6aefdfd4/attachment.html