fix #3471: avoid null being possible in the interface

This change also prohibits the same error to occur again in another
implementation of the same interface and should therefore be preferred
to just checking for null in the current interface implementation.

1 files changed, 3 insertions, 1 deletions

diff --git a/main/src/cgeo/geocaching/ui/AbstractCachingPageViewCreator.java b/main/src/cgeo/geocaching/ui/AbstractCachingPageViewCreator.java
index 568119e..9d87f2b 100644
--- a/main/src/cgeo/geocaching/ui/AbstractCachingPageViewCreator.java
+++ b/main/src/cgeo/geocaching/ui/AbstractCachingPageViewCreator.java
@@ -4,6 +4,8 @@ import cgeo.geocaching.activity.AbstractViewPagerActivity.PageViewCreator;
 
 import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
 
+import org.eclipse.jdt.annotation.NonNull;
+
 import android.os.Bundle;
 import android.view.View;
 
@@ -48,7 +50,7 @@ public abstract class AbstractCachingPageViewCreator<ViewClass extends View> imp
      * Restores the state of the view but just returns if not overridden.
      */
     @Override
-    public void setViewState(Bundle state) {
+    public void setViewState(@NonNull Bundle state) {
         return;
     }
 }