-
Key: BPMN2-253
-
Legacy Issue Number: 15055
-
Status: closed
-
Source: University of Stuttgart - ISW ( Frank Leymann)
-
Summary:
It is not precisely defined what definitions must be made in order to specify that a particular executable is to be invoked as an implementation of an operation of a service task (for example).
The specification should clearly spell out which definition are mandatory in order to capture the major scenarios, e.g. using an operation of WSDL port; using a java class;...
I submitted a document with more details on the problem area to issues@omg.org, without any response since weeks. I am happy to send this document to the person assigned to this issue, and discuss it.
-
Reported: BPMN 2.0b1 — Wed, 17 Feb 2010 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
- To "Table 8.80 - Interface attributes and model associations", add the following row:
implementationRef: Element[0..1] This attribute allows to reference a concrete artifact in the underlying implementation technology representing that interface, such as
a WSDL porttype. - To "Table 8.81 - Operation attributes and model associations", add the following row:
implementationRef: Element[0..1] This attribute allows to reference a concrete artifact in the underlying implementation technology representing that operation, such as
a WSDL operation. - Update the UML meta-model and XSD schema accordingly.
Disposition: Resolved
- To "Table 8.80 - Interface attributes and model associations", add the following row:
-
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Required definitions to invoke an existing function by means of a service task
- Key: BPMN2-253
- OMG Task Force: BPMN 2.0 FTF