Refactor Chromoting JNI code to use jni/Client (Java changes only).

remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java

Index: remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java
diff --git a/remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java b/remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java
index c7774f7fdd80a9e11e0edc2e31286b600fcfd3b4..3dea3691eb0566c898fd916cf5bd22ab3c20245a 100644
--- a/remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java
+++ b/remoting/android/javatests/src/org/chromium/chromoting/TouchInputStrategyTest.java
@@ -197,7 +197,10 @@ public class TouchInputStrategyTest extends InstrumentationTestCase {
     public void setUp() {
         mRenderData = new RenderData();
         mRemoteInputInjector = new MockRemoteInputInjector();
-        mInputStrategy = new TouchInputStrategy(mRenderData);
+
+        // TODO(lambroslambrou): Provide a mock Client implementation that doesn't call out to JNI,
+        // and mock the Client methods instead of using MockRemoteInputInjector here.
+        mInputStrategy = new TouchInputStrategy(mRenderData, null);
         mInputStrategy.setRemoteInputInjectorForTest(mRemoteInputInjector);
         mEventGenerator = new TouchEventGenerator();