Unparsable content <di:waypoint> detected / Bonita export

Users
1

The arrows disappear when importing a diagram previously exported from bpmn-js.I get this problem:

unparsable content <di:waypoint> detected
	line: 41
	column: 59
	nested error: unknown type <bpmndi:waypoint>

unparsable content <di:waypoint> detected
	line: 42
	column: 59
	nested error: unknown type <bpmndi:waypoint>

Cannot read property 'x' of undefined

The original bpmn file was exported with BonitaBPM.

Original bpmn: MyDiagram4.bpmn (3.5 KB)

Exported: diagram (2).bpmn (3.4 KB)

2

Problem solved with the descriptor:

{
  "name": "BonitaBPM",
  "uri": "http://www.bonitasoft.com/",
  "prefix": "di_1",
  "associations": [],
  "types": [
    {
      "name": "BonitaEdge",
      "extends": [ "bpmndi:BPMNEdge" ],
      "properties": [
        {
          "name": "waypoint",
          "isUnique": false,
          "isMany": true,
          "type": "dc:Point",
          "redefines": "di:Edge#waypoint",
          "xml": {
            "serialize": "xsi:type"
          }
        }
      ]
    }
  ],
  "emumerations": [ ]
}
3

Not sure if it is a bug on our side or not. Will look into this issue in a bit, too.

4

Great! Maybe has a simpler solution.

5

I just piped the diagram through BPMN 2.0 schema validation. It fails to validate and there is nothing much we can do about it. The validator reported the following issues:

[warning] SchemaLocation: schemaLocation value = 'schemaLocation http://www.omg.org/spec/BPMN/20100524/MODEL schemas/BPMN20.xsd' must have even number of URI's.
[error] cvc-complex-type.2.4.a: Invalid content was found starting with element 'di:waypoint'. One of '{"http://www.omg.org/spec/DD/20100524/DI":extension, "http://www.omg.org/spec/DD/20100524/DI":waypoint}' is expected.

The reported error relates to the import error you are seeing: Unparsable content <di:waypoint> detected.

6

Yes, the problem is not with bpmn-js, and can be fixed with the descriptor.