> Yeah - rewriting the whole data schema is a bit scary at this stage in > the project, although we may consider it for a later release. It's also > something I was reluctant to do, as having the content schema reflect > the true hierarchy of the content was one of the benefits we started off > with. If we change from parent-child relationships to reference > relationships, a lot of the argument for using a hierarchical model in > the first place becomes much weaker.
understood. i will also file a jsr-283 issue for that. short term i think either your workaround or a jackrabbit specific solution may be your only options. regards, david
