Charles,
Take a look at Node Type Definitions. I think this is really what you
want, NTDs are kind of like xml schemas, so you get the 'type safety' of
knowing that a child of 'reviews' is really a thing you know of as being a
review. But with the benefit of having it's own name.
See
http://jackrabbit.apache.org/node-types.html
cheers,
dave
----- Original Message -----
From: "Charles Johnson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, March 31, 2008 7:11 AM
Subject: Re: Node unfound, Node unsaved
Thanks Greg, i'll have a look at that. I don't know if things should be
different with JCR, but i was just proceeding on the standard xml:
<reviews>
<review isbn="xxxx">bar</review>
<review isbn="yyyy">foo</review>
</reviews>
CJ
Greg Klebus wrote:
Hi Charles
Just a short comment on your content model:
On Sun, Mar 30, 2008 at 9:17 PM, Charles Johnson <[EMAIL PROTECTED]>
wrote:
There seem to be problems with the most fundamental functionality. I'm
trying to create a single Node, /reviews, which I'll later use as the
root for /reviews/review[0..n]
Is there a reason for using same-name-siblings here? I think something
like that would be much easier to handle, and much more
self-explanatory:
/reviews/review-iphone
/reviews/review-ipodnano
or sth similar (depending on what's review subject).
Have you seen David's Model, esp Rule #4: Beware of Same Name Siblings
[1]? You might disagree, but should at least consider the consequences
of using SNSs.
[1]
http://wiki.apache.org/jackrabbit/DavidsModel#head-1df0224190c265f5156f037eb3f20e314fa6c4a7
Cheers
Greg
PS. Sorry if that's a well thought-through decision already :)
