Bug 980842 - Data assignement to "Interface" ignored in "ServiceTask".
Data assignement to "Interface" ignored in "ServiceTask".
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Core (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: DR6
: 6.0.0
Assigned To: Maciej Swiderski
Marek Baluch
Depends On:
  Show dependency treegraph
Reported: 2013-07-03 06:38 EDT by Marek Baluch
Modified: 2014-08-06 16:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-06 16:13:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
process definition (7.60 KB, application/xml)
2013-07-03 13:11 EDT, Marek Baluch
no flags Details

  None (edit)
Description Marek Baluch 2013-07-03 06:38:07 EDT
An data assignment to "Interface" in ioSpecification is ignore when a interface definition is present in the process. It would be nice if the user would see a warning message that it is ignored.

<bpmn2:ioSpecification id="InputOutputSpecification_1">
        <bpmn2:dataInput id="DataInput_4" name="Interface"/>
<bpmn2:dataInputAssociation id="DataInputAssociation_4">
        <bpmn2:assignment id="Assignment_4">
          <bpmn2:from xsi:type="bpmn2:tFormalExpression" id="FormalExpression_8">SimpleService</bpmn2:from>
          <bpmn2:to xsi:type="bpmn2:tFormalExpression" id="FormalExpression_7">DataInput_4</bpmn2:to>

Perhaps this ioSpecification part could be used in case the mandatory name attribute is missing in the interface element. The missing attribute is currently ignored by the validator.
Comment 1 Maciej Swiderski 2013-07-03 12:17:19 EDT
Marek, would it be possible to attach complete bpmn2 and if possible test case? But the most important is to have the bpmn2 itself. 

Comment 2 Marek Baluch 2013-07-03 13:11:19 EDT
Created attachment 768350 [details]
process definition

Hi, sure. My apologies for not doing it right away.

Please note that the interface on line 11 is missing it's 'name' attribute. The implementation name is set on line 75 using the 'Interface' parameter. This parameter will be empty in the WebServiceWorkItemHandler.
Comment 3 Maciej Swiderski 2013-07-04 11:47:37 EDT
fixed in master, the issue was due to service task handler was overriding the assignments done by the TaskHandler and thus it appeared to be ignored as it was simply reset.

Please note that not all parameters should be possible to set via data input assignments, for example following is a list that cannot:
- implementation - it's bpmn2 regular attribute of serviceTask
- operationRef - it's bpmn2 regular attribute of serviceTask

Moreover Interface, Operation are not used by the WebService implementation as it relies directly on operationRef attribute instead to find the right operation and interface. Although they are completely valid for Java service task.
Comment 7 Marek Baluch 2013-09-18 09:17:35 EDT
Verified on ER3.

Note You need to log in before you can comment on or make changes to this bug.