Troubleshooting
Problem
When a SOA or business process architect models service interfaces in BPMN, version 8.0.4 now offers the capability to reference a porttype defined in a WSDL file for the BPMN interface, which speeds the design by automatically importing the WSDL operations and messages into the BPMN model. However, the automatically filled BPMN item definitions for the operation parameter types point to the message names in the WSDL file, rather than types of the elements that makes up the message parameters. When transforming the model to UML or exporting to BPMN 2.0, the resulting UML model or BPMN file is missing the structure references.
Symptom
This problem originates when you reference a WSDL file for a BPMN interface. The problem may be spotted if you inspect the properties of the BPMN item definition. The structure corresponds to the target namespace of the WSDL file followed by the name of the message directly from the WSDL message's name attribute. The symptoms are seen after transforming the model to UML or exporting the model to BPMN 2.0 files. When transforming the BPMN model to UML, the types of the request and response messages for the UML operation are missing. When exporting to BPMN 2.0 files, the resulting BPMN file has a <bpmn:itemDefinition> tag with no structureRef attribute. If this file subsequently imported into Process Designer, generic untyped business objects will be generated for the message types.
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
10 September 2020
UID
swg21571493