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
java.lang.NullPointerException
at org.camunda.bpm.engine.impl.core.variable.VariableUtil.isJavaSerializationProhibited(VariableUtil.java:55)
at org.camunda.bpm.engine.impl.core.variable.VariableUtil.checkJavaSerialization(VariableUtil.java:82)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariableLocal(AbstractVariableScope.java:334)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:319)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:294)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:298)
at org.camunda.bpm.extension.mockito.delegate.VariableScopeFake.withVariable(VariableScopeFake.java:44)
Reason is, that a ProcessEngineConfiguration is required in the context to check, if a serialization check should be performed.
Of course we do not want to create a ProcessConfiguration and push it to the Context manually.
Simplest solution that worked well on our side is a patch in VariableScopeFake which overrides the following method:
This deactivates the serialization check in all cases.
Another option would be to patch AbstractVariableScope in Camunda, but seems to be unrealistic :-).
The text was updated successfully, but these errors were encountered:
CamundaMockito.delegateExecutionFake().withVariable("myVar", Variables.objectValue(myObject").create())
fails.java.lang.NullPointerException
at org.camunda.bpm.engine.impl.core.variable.VariableUtil.isJavaSerializationProhibited(VariableUtil.java:55)
at org.camunda.bpm.engine.impl.core.variable.VariableUtil.checkJavaSerialization(VariableUtil.java:82)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariableLocal(AbstractVariableScope.java:334)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:319)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:294)
at org.camunda.bpm.engine.impl.core.variable.scope.AbstractVariableScope.setVariable(AbstractVariableScope.java:298)
at org.camunda.bpm.extension.mockito.delegate.VariableScopeFake.withVariable(VariableScopeFake.java:44)
Reason is, that a ProcessEngineConfiguration is required in the context to check, if a serialization check should be performed.
Of course we do not want to create a ProcessConfiguration and push it to the Context manually.
Simplest solution that worked well on our side is a patch in VariableScopeFake which overrides the following method:
This deactivates the serialization check in all cases.
Another option would be to patch AbstractVariableScope in Camunda, but seems to be unrealistic :-).
The text was updated successfully, but these errors were encountered: