BPMN XSD Validation Errors

[squawkingmonkey]

I've upgraded an existing project to use Activiti 5.12 from 5.10.  The Activiti designer plugin has also been updated.  When trying to create the deployment artifacts, I'm getting the following errors in STS:

cvc-attribute.3: The value 'mail' of attribute 'activiti:type' on element 'serviceTask' is not valid with respect to its type, 'null'.
cvc-enumeration-valid: Value 'mail' is not facet-valid with respect to enumeration '[shell]'. It must be a value from the enumeration.

It seems like the XSD no longer supports the MailTask.  Any ideas on how to resolve these errors?

[ronald_van_kuij]

Remarkable… In another recent post (this day) I saw someone stating that he had to use activity:mail="mail" to get it working. Strange, but you might try that.

[squawkingmonkey]

I changed the bpmn file as you suggested; however, the generated XML still gets created with activity:type="mail".  I may have to recreate my workflows.

[ronald_van_kuij]

I did not say to change everything, just test with a manually adapted file and see if it still leads to an error.

[squawkingmonkey]

I only changed the activity:type to activity:mail.  When I create the deployment artifacts, the activity plugin generates an XML file in a temporary directory that still has the activity:type="mail" resulting in errors.

[ronald_van_kuij]

Then don't recreate te deployment artifacts… Just change it manually and deploy that e.g. In a testcase.

[squawkingmonkey]

Manually changing the XML to activity:mail="mail", packaging as a bar file, and deploying using Activiti Explorer results in a parse error: One of the attributes 'class', 'delegateExpression', 'type', 'operation', or 'expression' is mandatory on serviceTask.

[jbarrez]

Just to clarify: activiti:type="mail" is correct.  It just seems the newer versions of Eclipse now complain on the activiti namespace while earlier this wasn't the case.
For depoying a process, there is no difference, as the xml is validated against the bpmn xsd and the activiti attributes are checked by our parser.