Use jni_generator in Chromoting Android client

remoting/client/jni/chromoting_jni_runtime.h

Index: remoting/client/jni/chromoting_jni_runtime.h
diff --git a/remoting/client/jni/chromoting_jni_runtime.h b/remoting/client/jni/chromoting_jni_runtime.h
index 93d77bdae69c081f27cc825f289546c9ae24853e..bb356a13616e33bc814d28589bdefec7c486dea2 100644
--- a/remoting/client/jni/chromoting_jni_runtime.h
+++ b/remoting/client/jni/chromoting_jni_runtime.h
@@ -19,6 +19,8 @@ template<typename T> struct DefaultSingletonTraits;
 
 namespace remoting {
 
+bool RegisterJni(JNIEnv* env);
+
 // Houses the global resources on which the Chromoting components run
 // (e.g. message loops and task runners). Proxies outgoing JNI calls from its
 // ChromotingJniInstance member to Java. All its methods should be invoked
@@ -107,9 +109,6 @@ class ChromotingJniRuntime {
   // Detaches JVM from the current thread, then signals. Doesn't own |waiter|.
   void DetachFromVmAndSignal(base::WaitableEvent* waiter);
 
-  // Reference to the Java class into which we make JNI calls.
-  jclass class_;
-
   // Used by the Chromium libraries to clean up the base and net libraries' JNI
   // bindings. It must persist for the lifetime of the singleton.
   scoped_ptr<base::AtExitManager> at_exit_manager_;