Red Hat Bugzilla – Bug 1309950
JBDS Bpmn2 Diagram Editor - MetaData Tag Introduces Bad Namespace
Last modified: 2016-04-27 02:38:42 EDT
Created attachment 1128431 [details]
Description of problem:
1.1.4.Final introduces a bad namespace for the metadata tag which is required to implement asynchronous continuations in jbpm >= 6.3.
http://mswiderski.blogspot.com/2015/04/asynchronous-continuation-in-jbpm-63.html (see comments).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install bpm and rule dev tools
2. New-> jbpm process
3. Add service task
4. Go to general tab and add meta data
At least with the current XML namespace declarations
I would be open to an implementation for service tasks and other tasks that has a check box for async continuation, as opposed to the metadata button, as the meta thing is a bit cryptic. BC has this tick button, but unlike JBDS, BC is tied to a runtime version. Probably worth talking to Maciej about this one.
Created attachment 1128432 [details]
Also worth noting here that the async applies to more than just the service task, but also any work item handler, so whatever solution is chosen needs to apply to any task that can use async continuations,
Bob, please let us know, If you decided to fix metadata namespace or you have also added checkbox similarly to web designer.
I have checked latest BPMN2 Modeler for eclipse Mars and I know answer for my previous question.
Bob, sorry for needinfo flag and probably notification email you received.
The latest jbds tooling is:
BPMN2 Modeler - 1.2.3.CR2-v20160209-2002
Bug is fixed in:
BPMN2 Modeler - 1.2.3.Final-v20160218-1949-B212
When jbds tooling will contain newer BPMN2 Modeler, I will mark this as verified.
After "expert" mode is enabled (Preferences-BPMN2-Editor-Behavior), feature works well on:
Fixed in BPMN2 Modeler versions for