I had the same kind of issue. It seems most bpmn tools do not strictly stick to the OMG BPMN2 specification and modify the bpmn2 metamodel and resulting implementation. That’s why we get errors when importing models into bpmn.io.The same thing happens with the bpmn software namespaces in the files. I don’t get why software vendors implement a specification in a way that prevents full interoperability.
We have a similar problem, but it seems that our BPMN is valid. We are trying to integrate BPMN.io into Nuxeo (a DMS/ECM) and use the browserified version of BPMN.io. We’ve installed bpmn-js via npm as documented and used “browserify … --standalone tabjs …” to generate a single js file with all dependencies included. We are not using RequireJS.
The result is, that nothing is rendered. The error log shows a lot of errors like this one here
The surprising fact is, that the same BPMN file is working when opened with the cloud service BPMN.io. Therefore, it doesn’t seem to be a problem of the BPMN file, but rather a problem of including the JS correctly. The browserified JS is included as a resource in an XHTML template of Nuxeo. The BPMN file is delivered via a REST call to the camunda API. The JS file itself is stored in the Tomcat where camunda is running. The resulting SVG should be inserted into a DIV.
@nikku: Thanks for the fast response. Unfortunately that’s not the reason for the behavior
We confirmed, that the XML received by the JS function is identical to our file on disk.
A newer version of Chromium delivers some more detailed error messages
Error: unrecognized element <bpmn2:endEvent>
Error: unrecognized element <bpmn2:userTask>
Error: unrecognized element <bpmn2:sequenceFlow>
Error: unrecognized element <bpmn2:serviceTask>
Error: unknown type <"dc:Point" x=">
Error: unknown type <"dc:Point" x="59>
The namespace prefixes are however declared correctly. Further more we found this:
Warning Stacktrace :
at BaseHandler.19.ElementHandler.getPropertyForNode (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:3640:9)
at BaseHandler.19.ElementHandler.handleChild (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:3671:23)
at BaseHandler.19.BaseElementHandler.handleNode (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:3507:19)
at Object.handleOpen [as onopentag] (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:3844:26)
at emit (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5127:33)
at emitNode (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5132:3)
at openTag (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5313:3)
at Object.write (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5719:11)
at error (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5154:8)
at strictFail (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5174:22)
at openTag (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5263:7)
at Object.write (http://10.90.43.72:8080/bpmn-js/tab_js_browserified.js:5693:11)
We are looking into how to make our demo publicly available.