jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Neale" <michael.ne...@gmail.com>
Subject Re: Node Definitions
Date Fri, 27 Oct 2006 08:55:00 GMT
I *really* like the CND format that Jackrabbit uses to define, its so
declarative and at a glance almost anyone can understand the data structure
(needs very little training) - I hope someone is pushing that for JCR2 ! If
not, please do ! (and how can I vote !).

Yes I think interoperable node types is pretty critical for the
"swappability" - yes DDL is not compatable, but then things like hibernate
come along which will allow you to define the schema in the mapping files
for you (and have the DDL generated) - I would like to see JCR2 stick to a
common standard though, it would be another reason to use JCR other then a
vanilla RDBMS.


On 10/27/06, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> hi paul,
> On 10/26/06, Paul J DeCoursey <paul@decoursey.net> wrote:
> > Is there a way to define Node Types in a Implementation independent
> > manner?  This is my first look at Content Repositories so forgive me if
> > this question is naive.  I'm building a content management system and I
> > need to make it completely independent of Jackrabbit so that our
> > customers can just plug in whatever system they want.  For example once
> > IBM gets Content Manager JSR-170 ready. Does this make sense?  Or is it
> > that all systems will have their own way of defining node types and it
> > just cannot be done through JCR?
> jcr 2.0 will most probably cover node type management. jcr 2.0 is
> currently
> in the works, for more details please see
> http://jcp.org/en/jsr/detail?id=283.
> however, the final release is planned for may 2007, and this schedule is
> subject to change...
> another word of caution: don't expect too much wrt node type
> interoperability
> amongst different vendors. just like every database vendor has his 'own'
> brew
> of ddl syntax, most repository vendors will have specific restrictions
> and features.
> for example, currently none of the jcr implementations i know of support
> nt:unstructured (except jackrabbit of course ;-).
> cheers
> stefan
> >
> > Thanks
> >
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message