I see... what about storing the system's unique IDs as a property for the node instead? And then, use that property for indexing/search/location/whatever_you_do_with_the_current_system ?
Just an idea... Good luck! Jason Tesser escribió: > Well we are migrating our system to use JR and our data is structured. Our > system will be maintaining the structures as it currently does but the > content itself will be stored in JR. We have our own unique identifiers > which our system will need to keep for every piece of content in JR. I want > to limit what happens with a save of a piece of content. So I want to use > our systems unique ids for the uuid in JR. > > On 1/23/08, Fabián Mandelbaum <[EMAIL PROTECTED]> wrote: > >> Jason Tesser escribió: >> >>> Can I set the UUID of a node myself? If so how? >>> >>> >>> >> If I remember correctly the way JackRabbit generates the UUIDs for nodes >> is "magic" and "non-deterministic" ; meaning basically, that there's no >> guarantee that the same node will get the same UUID if stored (all other >> conditions, equal) on two different repos. >> >> Bottomline, I don't think it's a good idea to set the UUID yourself. >> >> If I may ask, which is your motivation to do so? >> >> Cheers. >> >> > > > >
