Open ThorbenLindhauer opened 9 years ago
This comment was imported from JIRA and written by user zZ6EdaWhat is this name?
This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Is this a valid workaround?
serviceTask.removeAttributeNs(org.camunda.bpm.model.bpmn.impl.BpmnModelConstants.CAMUNDA_NS, "delegateExpression")
This comment was imported from JIRA and written by user @nevries
This clearly also happens on
UserTask.setCamundaAssignee(null);
UserTask.setCamundaCandidateGroups(null);
...
Hence, setting assignee to null yields in a user task that is always assigned to a user with name empty string. Unpleasent behaviour...
This issue was imported from JIRA:
What is this name?
This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.See the test case below. It fails with this exception:
As you can see a "ServiceTaskDelegateExpressionActivityBehavior" was choosen - even if I set
I digged a bit into it and found that this results in havind the
Hence an empty string instead of null.
Not sure if this is a bug in the ModelAPI or if it should better be checked for emptry string in https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L1697 as done with expressions as well. https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L1703
Links: