Custom extension schema validation

I see that the org.activiti.bpmn.converter.BpmnXMLConverter class uses the BPMN2.0 schema and I see custom extension schemas (activiti-bpmn-extensions-n.nn), but I can’t seem to find any use of the custom extension schema for validation.

I do see some classes for custom extensions (FieldExtensionParser and FormPropertyParser are 2 examples), and I also see BpmnXMLUtil which adds these parsers, but I don’t see any way to add our own custom parsers. Am I missing something?

We are adding custom extensions of our own, and it’s not clear to me how to validate our XML against our custom schema. Is there a way to do that?


Good question. We haven’t been able to use the extensions XSD for validation yet. It seemed to be impossible to use both the standard BPMN 2.0 xsd and an extension XSD together to do one XSD validation run. If you have ideas on how this could be implemented that would be great.

Best regards,