Support variable changing in SDK interface and v8 native

plugins/org.chromium.sdk/src/org/chromium/sdk/internal/v8native/DebugSession.java

 // Copyright (c) 2009 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 package org.chromium.sdk.internal.v8native;
 
 import java.util.Collections;
 import java.util.logging.Level;
 import java.util.logging.Logger;
 
@@ skipping 275 matching lines @@
     return this.v8CommandProcessor.runInDispatchThread(callback, syncCallback);
   }
 
   public void maybeRethrowContextException(ContextDismissedCheckedException e) {
     // TODO(peter.rybin): make some kind of option out of this
     final boolean strictPolicy = true;
     if (strictPolicy) {
       throw new InvalidContextException(e);
     }
   }
+
+  public RelayOk maybeRethrowContextException(ContextDismissedCheckedException e,
+      SyncCallback syncCallback) {
+    // TODO(peter.rybin): make some kind of option out of this
+    final boolean strictPolicy = true;
+    if (strictPolicy) {
+      throw new InvalidContextException(e);
+    } else {
+      if (syncCallback != null) {
+        syncCallback.callbackDone(new InvalidContextException(e));
+      }
+      return new RelayOk() {

[apavlov, 2013/01/10 13:59:20]

Just occurred to me. Why don't you keep a singleton instance for this?

[Peter Rybin, 2013/01/10 14:10:44]

Mostly because I don't want to spoil outer namespace with a constant that is
never used (see fixed condition above). 

+        // It's ok, we called SyncCallback alright.
+      };
+    }
+  }
 }