|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page History* the mandatory parameters of the operation *are annotated* to retrieve the right values.
h3. Operations
h3. Identifying operations
h4. Create an instance of a process definition
The operation creating an instance of the process definition is identified by the annotation: {{operation="createInstanceProcOp"}}:
Because operation in WSDL 1.1 does not allow attribute extensibility, an operation is annotated by adding an {{operationAttr}} element as a child of the operation element. The {{operation}} attribute of {{operationAttr}} specifies the annotation. The value {{createInstanceProcOp}} identifies the operation creating a new instance of the process definition. An example of such an annotation is shown below.
{code}
<wsdl:portType name="Order">
<wsdl:operation name="newOrder">
<wsdl:portType name="Order">
<wsdl:operation name="newOrder">
<psa:operationAttr xmlns:psa="http://petals.ow2.org/se/activity/1.0">createInstanceProcOp</psa:operation>
operation="createInstanceProcOp" />
<wsdl:input message="NewOrderRequestMessage" />
<wsdl:output message="NewOrderResponseMessage" />
<wsdl:output message="NewOrderResponseMessage" />
</wsdl:portType>
{code}
{code}
If several operation are annotated by {{createInstanceProcOp}}, an error is thrown, and the deployment of the service unit is interrupted.
All parameters of the operation are used as parameter to create the instance of the process definition. {color:red}Peut être ajouter un mapping pour indiquer nom de la variable coté process et type ? Comment gérer les arborescences ?{color}
h4. Complete the current task of a process instance
Because operation in WSDL 1.1 does not allow attribute extensibility, an operation is annotated by adding an {{operationAttr}} element as a child of the operation element. The {{operation}} attribute of {{operationAttr}} specifies the annotation. The value {{completeTaskOp}} identifies the operation creating a new instance of the process definition. An example of such an annotation is shown below.
{code}
<wsdl:portType name="Order">
<wsdl:operation name="validOrder">
<psa:operationAttr xmlns:psa="http://petals.ow2.org/se/activity/1.0"
operation="completeTaskOp" />
<wsdl:input message="ValidOrderRequestMessage" />
<wsdl:output message="ValidOrderResponseMessage" />
</wsdl:operation>
</wsdl:portType>
{code}
If several operation are annotated by {{completeTaskOp}}, an error is thrown, and the deployment of the service unit is interrupted.
Some parameters are expected for this operation:
* identifier of the process instance,
* identifier of the task to complete,
* completion status.
These parameters are also annotated into the WSDL, more precisely in the XSD part. {color:red}Est ce mieux dans le XSD ou dans la definition de l'operation ? Ne serait-il pas mieux d'utiliser l'annotation au niveau de l'operation et de donner les paramètres par une expression XPath ? Même question pour les valeurs OK, KO de completaion de la tache ? {colore}