Bug 1309950

Summary: JBDS Bpmn2 Diagram Editor - MetaData Tag Introduces Bad Namespace
Product: [Retired] JBoss BPMS Platform 6 Reporter: Justin Holmes <jholmes>
Component: Eclipse ToolingAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Jozef Marko <jomarko>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0   
Target Milestone: ---   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:42:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
test.bpmn2
none
Stacktrace none

Description Justin Holmes 2016-02-19 04:51:32 UTC
Created attachment 1128431 [details]
test.bpmn2

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):
1.1.4

How reproducible:
100%

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

Actual results:
        <tns:metaData tns:name="customAsync">
          <tns:metaValue><![CDATA[true]]></tns:metaValue>
        </tns:metaData>


Expected results:
        <tns:metaData name="customAsync">
          <tns:metaValue><![CDATA[true]]></tns:metaValue>
        </tns:metaData>

At least with the current XML namespace declarations

Additional info:
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.

Comment 1 Justin Holmes 2016-02-19 04:52:01 UTC
Created attachment 1128432 [details]
Stacktrace

Comment 3 Justin Holmes 2016-02-19 05:47:25 UTC
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,

Comment 4 Jozef Marko 2016-02-22 07:14:38 UTC
Bob, please let us know, If you decided to fix metadata namespace or you have also added checkbox similarly to web designer.

Comment 5 Jozef Marko 2016-02-22 08:10:25 UTC
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:
jbds-9.1.0.Beta2_jbdsis-9.0.0.Beta1
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.

Comment 6 Jozef Marko 2016-03-23 09:34:34 UTC
After "expert" mode is enabled (Preferences-BPMN2-Editor-Behavior), feature works well on:
jbds-9.1.0.Beta2_jbdsis-9.0.0.Beta1
jbds-8.1.0.GA_jbdsis-8.0.6.CR3

Comment 7 Robert (Bob) Brodt 2016-03-23 14:19:15 UTC
Fixed in BPMN2 Modeler versions for
Luna: 1.1.6.CR1-v20160318-1403-B1303
Mars: 1.2.4.CR1-v20160318-1302-B107
Neon: 1.3.0.Beta1-v20160318-1302-B41