[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ozone IDs through XML import/export



Am I correct in assuming the presence of object IDs in the Ozone export XML
means that internal database IDs [i.e.
ozoneobject.container().id().getValue()] will remain invarient through a
cycle of exporting the entire database as XML and then importing it to a
fresh and empty database?

I'm in the process of hacking together a restricted object description model
for some later development that requires all objects to have a unique ID and
reference one another via this ID rather than containment or Java
references. (Don't ask: it makes sense in context :). Using the internal
Ozone methodology of ID assignment is the easiest method of unique ID
assignment by far, but invarience across imports/exports becomes
important...

Reason
CTO, VIPMobile