You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a custom serialisable field of mine, the problem is, if it is not initialised or is null, the cache.put("existingDataSources", __result);; will throw a java.lang.NullPointerException: key == null || value == null exception.
Can this be changed to allow null values? Any reasons, why this is not possible yet?
Btw, the code generator is generating double ; as you can see in my code example... Not a big deal though, so I'm just mentioning it here...
With cache enabled, generated code may look like following:
This is a custom serialisable field of mine, the problem is, if it is not initialised or is null, the
cache.put("existingDataSources", __result);;
will throw ajava.lang.NullPointerException: key == null || value == null
exception.Can this be changed to allow null values? Any reasons, why this is not possible yet?
Btw, the code generator is generating double ; as you can see in my code example... Not a big deal though, so I'm just mentioning it here...
PS: currently I'm using following version:
The text was updated successfully, but these errors were encountered: