The order of multi-valued properties IS restored within Jackrabbit, but jcr:deref doesn't respect that order... so you CAN derefernce manually without losing the order. The problem is I'm using query based ORM(OCM) strategy (like grafitto jcr mapping), and your solution seems to be pretty messy to implement. How exactly do you control the order within the orderable child nodes?
Brian Thompson-5 wrote: > > On 2/26/07, avim <[EMAIL PROTECTED]> wrote: >> >> >> What is the score in this case? >> Anyway I don't think it will give me the desired order, and there is a >> need >> for kind of predicates/relations with extra data/connection objects >> anyway. >> Any advice/best practices? >> > > > In my application, I had one instance where I needed to keep track of an > ordered list of references to other nodes in the repository. At first > glance, using a multi-valued property on my tracker node seemed like the > best idea. Since that doesn't guarantee any sort of order, I resorted to > orderable child nodes, each one of which has a property that refers to the > desired node. It's a little less elegant, but until Jackrabbit supports > orderable multi-valued properties, it will have to do. > > -Brian > > -- View this message in context: http://www.nabble.com/many-to-many-relations-flexible-hierarchies-references-tf3252566.html#a9249663 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
