Implement WebViewDatabase's hasFormData API for chromium based webview.

android_webview/java/src/org/chromium/android_webview/AwFormDatabase.java

 // Copyright 2013 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.android_webview;
 
 import org.chromium.base.JNINamespace;
 
 /**
  * Exposes a subset of Chromium form database to Webview database for managing autocomplete
  * functionality.
  */
 @JNINamespace("android_webview")
 public class AwFormDatabase {
 
+    public static boolean hasFormData() {

[benm (inactive), 2013/04/29 18:00:03]

Rather than having these as statics, can they call through to the
AwFormDatabaseService directly (i.e. they have a ptr to the native instance,
like most of our JNI)

Then this class would be AwForDatabaseService rather than AwFormDatabase.

[sgurun-gerrit only, 2013/04/29 19:32:39]

We could. I think AwBrowserContext is the proper way to get this pointer since
these objects are owned by the AwBrowserContext, however at the moment
awbrowsercontext java and native sides are disconnected. I think Joth has a TODO
for this. 

My feeling is to leave this as static, with a TODO explaining how we are
thinking of solving it, and then handling this after that. Or I can address
AwBrowserContext right away. I am fine with both. Let me know if you have a
preference.

On 2013/04/29 18:00:03, benm wrote:

+        return nativeHasFormData();
+    }
+
     public static void clearFormData() {
         nativeClearFormData();
     }
 
     //--------------------------------------------------------------------------------------------
     //  Native methods
     //--------------------------------------------------------------------------------------------
+    private static native boolean nativeHasFormData();
+
     private static native void nativeClearFormData();
 }