Problems migrating from Activiti 5.16.3 to 5.17.0

[stephan_bauer]

Dear Activiti-Team,

we are currently under development of a business-critical application with Activiti. Because we were facing serious problems with XA-Transactions which seemed similar to what is described in

http://forums.activiti.org/content/activitioptimisticlockingexception-even-simplest-process

we decided to migrate to 5.17.0, because it was said that the new AsyncExecutor seemed to help in that case.

But the migration confronted us with other serious problems and so we are currently in a deadlock situation! If we cannot find a solution rather fast, we will have to abandon Activiti from our project, even if this is painful for us because there are already 4 Process-Modells with lots of ServiceTasks and other stuff.

we have already overcome the problem described in http://forums.activiti.org/content/javalangclasscastexception-standaloneinmemprocessengineconfigurat... (not nice, but we did it).

But now we had to find out, that the new Modeler removes our class fields from the models which is a very bad as we make heavy use of them. I found http://jira.codehaus.org/browse/ACT-2212 and so we tried to continue modelling with 5.16.3 and importing and deploying the models directly in 5.17.0 WITHOUT using the new modeler. But now we get the following error message when trying to deploy one of the models (the famous red box in the explorer) complaining about the name of a „Message“ element:

<message id="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg" name="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg'/> 

    <intermediateCatchEvent id="sid-59BB7064-D0C2-4306-B8BE-4D2FD669B57E" name="Produktinstanz wegen Fehler abgebrochen">
      <messageEventDefinition messageRef="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg'/>
    </intermediateCatchEvent>
‍‍‍‍‍‍‍

The error-Message reads:

Create of BPMN XML failed: cvc-datatype-valid.1.2.1: “http://www.activiti.org/processdef: Produktinstanz-wg-Fehler-abgebrochen-Msg“ ist kein gültiger Wert für NCName

which means that it is not a valid value for NCName.

The originally imported definition from the 5.16.3 model was without that http://-Prefix:

<code>
<message id="Produktinstanz-wg-Fehler-abgebrochen-Msg" name="Produktinstanz-wg-Fehler-abgebrochen-Msg"/>

    <intermediateCatchEvent id="sid-59BB7064-D0C2-4306-B8BE-4D2FD669B57E" name="Produktinstanz wegen Fehler abgebrochen">
      <messageEventDefinition messageRef="Produktinstanz-wg-Fehler-abgebrochen-Msg"/>
    </intermediateCatchEvent>
<code>

=> Why does Activiti prepend such a prefix first when it can't handle it afterwards? Can we somehow get rid of that?

Many thanks in advance,
Stephan

[stephan_bauer]

So the question is: => Why does Activiti prepend such a prefix first when it can't handle it afterwards? Can we somehow get rid of that?

[jbarrez]

This was a bug, as it comes in software. Someone in the community noticed it quickly and Vasile has fixed it in the meantime on master. There is now a unit test that tests for this specific regression.