*** Description of problem: In business process model, user can define some 'Error', which have 'Name', 'Error Code' and 'Data Type'. General workflow is: 1. Define 'Data Type' in Process properties -> Definitions 2. Define 'Error' in Process properties -> Definitions 3. Model business process But there is another option: 1. Start model business process 2. Create 'Data Type' or 'Error' from element, which need it. *** Version-Release number of selected component (if applicable): jbds-8.1.0.CR1_jbdsis-8.0.1.CR1 - BPMN2 Modeler 1.1.2.Final *** Steps to Reproduce: 1. Create simple process (StartEvent -> ScriptTask -> EndEvent) 2. Add ErrorBoundaryEvent to ScriptTask 3. Double click on ErrorBoundaryEvent 4. Edit the first event in 'Event Definitions' table 5. Click plus button next to 'Error' combo 6. Click plus button next to 'Data Type' combo 7. Type 'java.lang.RuntimeException' to input box 'Structure' 8. Select 'java.lang.RuntimeException' via 'Browse Types...' button *** Actual results: In step 7. error like "Characters xyz are not valid - expecting a Java Package name" In step 8. 'java.lang.RuntimeException' is correctly selected *** Expected results: 'java.lang.RuntimeException' is correctly selected in step 7. without need of step 8.
This was also addressed by bug https://bugzilla.redhat.com/show_bug.cgi?id=1189454 Fixed in 1.1.4.20150618* builds.
Fix looks good on BPMN2 Modeler 1.1.4.201506182307.
I have to reassign this BZ. I am again not able to add data type via given plus button. I can only edit existing one. Reproduced on: jbds-9.0.0.CR1_jbdsis-9.0.0.Alpha1
Fixed in: Luna build 1.1.4.201510291907 Mars build 1.2.1.201510291906 I will coordinate with Paul Leacu to figure out when this will be mirrored in JBDS integration stack.
Bob, thank. Fix looks good. I will mark as verified when fix will be mirrored in JBDS integration stack.
Verified on jbdsis-8.0.5, BPMN2 Modeler 1.1.4.Final