On Aug 11, 2010, at 12:34 PM, "Fabio Barbon" <[email protected]> wrote:
> Hi > >> -----Messaggio originale----- >> Da: Jukka Zitting [mailto:[email protected]] >> ... >> A reference always points to the current version of a referenceable >> node. > > > Ok, I see. > > What I need instead is that a reference points to the version of the > referenceable node > at the time the reference was set. > > Isn't this behavior making sense to anybody else here? > > Example: B is a car model, A is a mortgage car sale. > A.model indicates the model of car sold in sale A. > There are two B versions: B1 is model 2007, B2 is model 2009. > Moreover, there are two A versions: A1 is when the car was sold and > first rate paid, in year 2008 (at this time A1.model = B1). > A2 is when the second rate was paid, in 2010. > In this case A2.model should be B1, not B2, because the object of sale A > is always B1. > Not sure how literally to take this, but I wouldn't model (no pun intended) different model years of a car with versions of the same node. Parts lists, recall notifications, user manuals, etc. are disjoint from year to year. > > >> If you want to refer to a frozen version of such a node, then >> you need to set the reference to the jcr:uuid of the frozen node. >> > > The drawback I see here is that whenever you checkin a referred node you > need to update all references to it > (that's what I actually did in the meantime). > > Thanks for the reply, best regards > -Fabio >
