5.4. “Third-class” objects – arrays
The JDO specification does not use the term “third-class,” but I have coined it here to describe array support in JDO. Support for array objects is not required in JDO, it is an optional feature. Where arrays are supported by an implementation, the change tracking feature, by which second-class objects notify their owning first-class objects of changes, is itself optional. Thus, although a particular vendor may provide an array implementation that does fulfill the change tracking semantics of second-class objects, this behavior should not be relied upon. Portable applications that make use of array persistence must implement functionality by which changes to the array contents is reflected by explicitly making ...
Get Java™ Data Objects now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
