kbowers-ibm commented on PR #3445:
URL: 
https://github.com/apache/incubator-kie-tools/pull/3445#issuecomment-3927860908

   Thanks @jomarko and @ljmotta for the feedback!
   I've fixed the problem of the interface persisting when morphing to a custom 
task, nice catch!
   Regarding the ID issue, I'm no bpmn expert, but afaik there's no issue 
there. For reference this is what happens in the old bpmn editor:
   ```
     <bpmn2:interface 
id="_59E44166-295D-413F-A8F4-28808A278CDF_ServiceInterface" name="qwe" 
implementationRef="qwe">
       <bpmn2:operation 
id="_59E44166-295D-413F-A8F4-28808A278CDF_ServiceOperation" name="asd" 
implementationRef="asd">
         
<bpmn2:inMessageRef>_59E44166-295D-413F-A8F4-28808A278CDF_InMessage</bpmn2:inMessageRef>
         
<bpmn2:outMessageRef>_59E44166-295D-413F-A8F4-28808A278CDF_OutMessage</bpmn2:outMessageRef>
       </bpmn2:operation>
     </bpmn2:interface>
       <bpmn2:serviceTask id="_59E44166-295D-413F-A8F4-28808A278CDF" 
drools:serviceimplementation="Java" drools:serviceinterface="qwe" 
drools:serviceoperation="asd" name="Task" implementation="Java" 
operationRef="_59E44166-295D-413F-A8F4-28808A278CDF_ServiceOperation">
   ```
   As you can see they all have the exact same id, as the serviceTask and then 
append on something at the end. My understanding is that id's are essentially 
just random strings and are not defined in the bpmn spec, e.g. this is what the 
operation should consist of:
   <img width="715" height="585" alt="image" 
src="https://github.com/user-attachments/assets/7c5c5e5a-cf13-43fc-b1ed-205b689000d9";
 />
   So it has to have the inMessageRef and the outMessageRef is optional.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to