<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problems migrating from Activiti 5.16.3 to 5.17.0 in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178900#M132030</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dear Activiti-Team,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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 &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.activiti.org/content/activitioptimisticlockingexception-even-simplest-process" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/content/activitioptimisticlockingexception-even-simplest-process&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;we decided to migrate to 5.17.0, because it was said that the new AsyncExecutor seemed to help in that case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;we have already overcome the problem described in &lt;/SPAN&gt;&lt;A href="http://forums.activiti.org/content/javalangclasscastexception-standaloneinmemprocessengineconfiguration-cannot-be-cast" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/content/javalangclasscastexception-standaloneinmemprocessengineconfiguration-cannot-be-cast&lt;/A&gt;&lt;SPAN&gt; (not nice, but we did it).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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 &lt;/SPAN&gt;&lt;A href="http://jira.codehaus.org/browse/ACT-2212" rel="nofollow noopener noreferrer"&gt;http://jira.codehaus.org/browse/ACT-2212&lt;/A&gt;&lt;SPAN&gt; 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:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;&amp;lt;message id="&lt;A href="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg&lt;/A&gt;" name="&lt;A href="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg%22/" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg'/&lt;/A&gt;&amp;gt; &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;intermediateCatchEvent id="sid-59BB7064-D0C2-4306-B8BE-4D2FD669B57E" name="Produktinstanz wegen Fehler abgebrochen"&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;messageEventDefinition messageRef="&lt;A href="http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg%22/" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/processdef:Produktinstanz-wg-Fehler-abgebrochen-Msg'/&lt;/A&gt;&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/intermediateCatchEvent&amp;gt;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The error-Message reads:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Create of BPMN XML failed: cvc-datatype-valid.1.2.1: “&lt;/SPAN&gt;&lt;A href="http://www.activiti.org/processdef" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/processdef&lt;/A&gt;&lt;SPAN&gt;: Produktinstanz-wg-Fehler-abgebrochen-Msg“ ist kein gültiger Wert für NCName&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;which means that it is not a valid value for NCName.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The originally imported definition from the 5.16.3 model was without that &lt;/SPAN&gt;&lt;A href="http://-Prefix" rel="nofollow noopener noreferrer"&gt;http://-Prefix&lt;/A&gt;&lt;SPAN&gt;:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &amp;lt;message id="Produktinstanz-wg-Fehler-abgebrochen-Msg" name="Produktinstanz-wg-Fehler-abgebrochen-Msg"/&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;intermediateCatchEvent id="sid-59BB7064-D0C2-4306-B8BE-4D2FD669B57E" name="Produktinstanz wegen Fehler abgebrochen"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;messageEventDefinition messageRef="Produktinstanz-wg-Fehler-abgebrochen-Msg"/&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/intermediateCatchEvent&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;=&amp;gt; Why does Activiti prepend such a prefix first when it can't handle it afterwards? Can we somehow get rid of that?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Many thanks in advance,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Stephan&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Mar 2015 18:16:19 GMT</pubDate>
    <dc:creator>stephan_bauer</dc:creator>
    <dc:date>2015-03-10T18:16:19Z</dc:date>
    <item>
      <title>Problems migrating from Activiti 5.16.3 to 5.17.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178900#M132030</link>
      <description>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-proces</description>
      <pubDate>Tue, 10 Mar 2015 18:16:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178900#M132030</guid>
      <dc:creator>stephan_bauer</dc:creator>
      <dc:date>2015-03-10T18:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: Problems migrating from Activiti 5.16.3 to 5.17.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178901#M132031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;So the question is: =&amp;gt; Why does Activiti prepend such a prefix first when it can't handle it afterwards? Can we somehow get rid of that?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Mar 2015 18:18:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178901#M132031</guid>
      <dc:creator>stephan_bauer</dc:creator>
      <dc:date>2015-03-10T18:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: Problems migrating from Activiti 5.16.3 to 5.17.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178902#M132032</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Mar 2015 08:42:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/problems-migrating-from-activiti-5-16-3-to-5-17-0/m-p/178902#M132032</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2015-03-17T08:42:52Z</dc:date>
    </item>
  </channel>
</rss>

