Class cast exception when using BPMN Transactions. about camunda-platform-7-reactor HOT 5 CLOSED

Hi zapata. Thanks for reporting this. I never worked with "transaction" in camunda before, so I just missed this.

To fix, have a look into RegisterAllBpmnParseListener. It adds a listener to every transition that fires an event to the bus. In case of transaction, I do:

 @Override
  public void parseTransaction(Element transactionElement, ScopeImpl scope, ActivityImpl activity) {
    addExecutionListener(activity);
  }

  void addExecutionListener(final ActivityImpl activity) {
    for (String event : EXECUTION_EVENTS) {
      activity.addListener(event, executionListener);
    }
  }

which seems to be wrong. Maybe (would have to check), we need a behavior like sequenceFlows:

  void addExecutionListener(final TransitionImpl transition) {
    transition.addListener(EVENTNAME_TAKE, executionListener);
  }

from camunda-platform-7-reactor.

I asked the forum: https://forum.camunda.org/t/what-events-are-allowed-on-the-transaction-element/910

from camunda-platform-7-reactor.

According to https://forum.camunda.org/t/how-to-get-the-elementtype-of-a-modelinstanceelement-that-is-not-a-flowelement-transaction/912/2 this should work with 7.5.0 is that an option for you?

I think I will implement a version hook, where events for start/end transaction are only fired if its >= 7.5 This extension does not have the manpower to support multiple versions over time.

from camunda-platform-7-reactor.

7.5 is good for me!

As a quick fix i just removed the BPMN Transaction which is almost useless anyway (at least in Camunda).

Many thanks for you quick answer.

from camunda-platform-7-reactor.

No prob. I can confirm that 7.5 works. I will add a version switch to the transaction element so no events will get fired for version < 7.5

from camunda-platform-7-reactor.