---

WOJavaDoc

Radar #2370377

Locking operations aren't supported in the client side of a Java Client application.

Description:

Locking is not implemented in Java Client's distribution layer (especially EODistributedObjectStore), but there is public API in those classes that makes it appear otherwise. The EODistributedObjectStore method isObjectLockedWithGlobalID always returns false because locking isn't supported in the client. Similarly, the EODistributedObjectStore method lockObjectWithGlobalID raises an exception. The EOEditingContext locking methods (lockObjectWithGlobalID, lockObject, locksObjectBeforeFirstModification, setLocksObjectBeforeFirstModification, and isObjectLockedWithGlobalID) cannot be used on the client side; lockObjectWithGlobalID and lockObject raise on first use; locksObjectBeforeFirstModification and setLocksObjectBeforeFirstModification trigger a raise if set to true and you modify an object; and isObjectLockedWithGlobalID always returns false.

Workaround:

None.

Radar #2574946

WOXMLCoding has an additional method.

Description:

There is a new classForCoder() method in the WOXMLCoding interface that is the same as the classForCoder() method in the NSCoding interface. The WOXMLCoder uses the method to specify the type attribute of an encoded object element.

For the classes with built-in support from the WOXMLCoder that implement the NSCoding interface, the classForCoder() method that already exists gets used.

Workaround:

N/A

Radar #2855641

In-memory qualification and sorting differs slightly from SQL.

Description:

EOQualifiers are generally used to generate SQL, but they also can be used for "in-memory" qualification, where the results are calculated directly. Due to differences in the semantics between Java and SQL, there may be edge cases where the results can differ, particularly if null values are involved. This release note describes how in-memory qualification treats nulls.

From EOQualifier's point of view, nothing is equal to null. However, isEqual or isNotEqual will treat null == null. Other operators such as <, <=, >, =>, etc. all return false if either operand is null. That is, null == null, but !(null <= null).

This behavior is intended to be as close to SQL as possible.For EOSortOrdering, null is essentially treated as negative infinity. An array with null (or NSKeyValueCoding.NullValue) will have those elements sorted toward the very beginning if the sort selector is CompareAscending or at the very end for CompareDescending.

Workaround:

None.

---