When I add a Data Type definition to a process, the BPMN 2 editor is creating the item definition as expected, but it's also creating a ton of message entries, e.g. <bpmn2:message id="_Message_60" itemRef="_ItemDefinition_1333" name="Applicant_getAge_Result"/> <bpmn2:message id="_Message_61" itemRef="_ItemDefinition_1335" name="Applicant_getDob_Result"/> <bpmn2:message id="_Message_62" itemRef="_ItemDefinition_1335" name="Applicant_setDob_dob"/> <bpmn2:message id="_Message_63" itemRef="_ItemDefinition_1333" name="Applicant_getCreditScore_Result"/> <bpmn2:message id="_Message_64" itemRef="_ItemDefinition_1333" name="Applicant_setCreditScore_creditScore"/> < … snipped many more …> In addition, it's creating a bunch of operation definitions which fail BPMN 2 validation, leaving me with quite a few errors in the Problems view: <bpmn2:operation id="_Operation_60" implementationRef="getAge" name="getAge"> <bpmn2:outMessageRef>_Message_60</bpmn2:outMessageRef> </bpmn2:operation> "Operation has missing or incomplete In Message PreQualProcess.bpm" Any idea what's going on here? I should be able to just add the type definition without generating the message and operation refs, right? Steps I'm following now are: 1) Pull up Process Properties view 2) Select Definitions 3) Add data type via + icon next to 'Data Type List'
Created attachment 852725 [details] Applicant.java Attaching Applicant class which produces the issue when added as a data type in the process definition.
FYI - I set the proposed blocker flag here because this is a high-visibility issue from a user standpoint. I will look at a workaround, but it will almost certainly involve hacking the xml directly.
I think this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1052918 Keith, is it possible for you to grab the latest bpmn2 editor from here: http://download.eclipse.org/bpmn2-modeler/updates/luna/1.0.2/ and retest?
This is fixed in version 1.1.3 of the BPMN2 Modeler and is included in JBDSIS 8.0.3.GA and JBTIS 4.2.3.Final
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.