Problem wrongly reported with missing time to live

[cybermotier]

Describe the bug

Editing a BPMN, a problem is reported for the BPMN with the Time to live field marked as invalid. The displayed message is: Time to live must be defined.
But a value (14) was set.

Steps to reproduce

1. Open a BPMN
2. Invoke Save
3. Time to live field displayed as missing when a value is provided

Expected behavior

No problem report

Environment

Camunda Modeler system information

• Version: 5.15.0
• Operating System: Windows 10 amd64
• Plugins:
• Execution Platform: BPMN - Camunda Platform 7

Additional context

No response

[smbea]

Thanks for reporting, I can reproduce the issue. We'll look into it.

[marstamm]

[Root Cause]

Soooo, usually we reuse the parsed moddle when we do the linting, but on save we only pass the XML. That means that we need to parse it in linting. For some reason, we do not have the camunda moddle extension in @camunda/linting, so all camunda: properties are ignored. The fix should be as simple as adding a moddle extenstion to @camunda/linting

[philippfromme]

For some reason, we do not have the camunda moddle extension in @camunda/linting, so all camunda: properties are ignored. The fix should be as simple as adding a moddle extenstion to @camunda/linting

Ooopsie!

[marstamm]

As it turns out, it is not as simple as adding another extension. As described in bpmn-io/moddle#45, moddle does not allow you to have attributes with the same name, even in different namespaces. Unfortunately, we do have overlaps for modelerTemplate attributes.

As a workaround, we can provide the diagram type (C7/C8) in the tab Config and select the needed moddle extension:

camunda-modeler/client/src/app/TabsProvider.js

Lines 248 to 251 in 3356ba8

	return new BpmnLinter({
	modeler: 'desktop',
	plugins
	});