JavaCallback: Remove non-UserParam JavaConfiguration.requiresJavaCallbackCode()

Method was encapsulated in commit d4e8ecc3b4f68b86d95ec951971a0fea20217988
and questioned whether it is required.

The non-userParam callback case adds no additional code requirements.
Both, callback with and without userParam shares same code path
and the respective native static fields.
Only that the non-userParam code path adds additional native static fields,
but all code sections are produced in both cases.

Passed all unit tests.

1 files changed, 0 insertions, 7 deletions

diff --git a/src/java/com/jogamp/gluegen/JavaConfiguration.java b/src/java/com/jogamp/gluegen/JavaConfiguration.java
index 95e1480..107b8c3 100644
--- a/src/java/com/jogamp/gluegen/JavaConfiguration.java
+++ b/src/java/com/jogamp/gluegen/JavaConfiguration.java
@@ -2517,11 +2517,4 @@ public class JavaConfiguration {
   /** Mapped binding name to {@link JavaCallbackInfo} */
   /* pp */ final Map<String, JavaCallbackInfo> setFuncToJavaCallbackMap = new HashMap<String, JavaCallbackInfo>();
   final Set<String> emittedJavaCallbackUserParamClasses = new HashSet<String>();
-
-  /** Returns true if a method binding requires specific java callback code */
-  final boolean requiresJavaCallbackCode(final String bindingName) {
-      final JavaCallbackInfo jcbi = setFuncToJavaCallbackMap.get(bindingName);
-      return null != jcbi && !jcbi.cbUserParamIsDefined;
-  }
-
 }