Android Allows nested namespace in @JNINamespace annotation.

base/android/jni_generator/SampleForTests.java

 // Copyright (c) 2012 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.example.jni_generator;
 
 // This class serves as a reference test for the bindings generator, and as example documentation
 // for how to use the jni generator.
 // The C++ counter-part is sample_for_tests.cc.
 // jni_generator.gyp has a jni_generator_tests target that will:
 //   * Generate a header file for the JNI bindings based on this file.
 //   * Compile sample_for_tests.cc using the generated header file.
 //   * link a native executable to prove the generated header + cc file are self-contained.
 // All comments are informational only, and are ignored by the jni generator.
 //
 // This JNINamespace annotation indicates that all native methods should be
 // generated inside this namespace, including the native class that this
 // object binds to.
-@JNINamespace("content")
+@JNINamespace("base::android")
 class SampleForTests {
   // Classes can store their C++ pointer counter part as an int that is normally initialized by
   // calling out a nativeInit() function.
   int nativePtr;
 
   // You can define methods and attributes on the java class just like any other.
   // Methods without the @CalledByNative annotation won't be exposed to JNI.
   public SampleForTests() {
   }
 
@@ skipping 117 matching lines @@
     }
 
     @NativeCall("InnerClass")
     private static native int nativeInnerFunction();
 
     @NativeCall("InnerClass")
     private static native String nativeInnerMethod(int nativeCPPClass);
 
   }
 }