//Deal with an optimistic locking failure.

    public void handleOptimisticLockingFailureByLastWriteWins(EOGeneralAdaptorException lockingException) {

        //Get the info dictionary that is created when the exception is thrown.

        NSDictionary info = lockingException.userInfo();

        //Determine the adaptor operation that triggered the optimistic locking failure.

        EOAdaptorOperation adaptorOperation = (EOAdaptorOperation)info.objectForKey(EOAdaptorChannel.FailedAdaptorOperationKey);

        int operationType = adaptorOperation.adaptorOperator();

        //Determine the database operation that triggered the failure.

        EODatabaseOperation dbOperation = (EODatabaseOperation)info.objectForKey(EODatabaseContext.FailedDatabaseOperationKey);

        //Retrieve the enterprise object that triggered the failure.

        EOEnterpriseObject failedEO = (EOEnterpriseObject)dbOperation.object();

        //Retrieve the dictionary of values involved in the failure.

        NSDictionary valuesInFailedSave = adaptorOperation.changedValues();// 1

        NSLog.out.appendln("valuesInFailedSave: " + valuesInFailedSave);

        //Take action based on the type of adaptor operation that triggered the optimistic locking failure.

        if (operationType == EODatabaseOperation.AdaptorUpdateOperator) {

            //Recover by essentially ignoring the optimistic locking failure and committing the

            //changes that originally failed. This is a last write wins policy.

            //Overwrite any changes in the database with the eo's values.

            failedEO.reapplyChangesFromDictionary(valuesInFailedSave); // 2

        } else { //The optimistic locking failure was causes by another type of adaptor operation, not an update.

            throw new NSForwardException(lockingException, "Unknown adaptorOperator " + operationType + " in optimistic locking exception.");

        }

        session().defaultEditingContext().saveChanges();

    }