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.