Petals Ant Tasks

Support to select a flow step randomly

Details

  • Description:
    Hide

    When several flow steps match the given criteria, instead of using always the same flow (using parameter 'row'), we should be able to select a flow step randomly:

    <petals-extract-flow-step-info refid="aggregated-flows" selectRandomly="true">
       <flowStepCriteria name="traceCode" value="consumeExtFlowStepBegin" />
       <flowStepCriteria name="flowStepInterfaceName" value="{http://petals.ow2.org/}HelloWorldService" />
       <flowStepCriteria name="flowStepServiceName" value="{http://petals.ow2.org/}HelloWorldService" />
       <flowStepCriteria name="flowStepOperationName" value="{http://petals.ow2.org/}sayHello" />
       <flowStepInfo attribute="flowInstanceId" property="initial-flow-instance-id" />
       <flowStepInfo attribute="flowStepId" property="initial-flow.flow-step-id.rmi-consumer" />
    </petals-extract-flow-step-info>
    Show
    When several flow steps match the given criteria, instead of using always the same flow (using parameter 'row'), we should be able to select a flow step randomly:
    <petals-extract-flow-step-info refid="aggregated-flows" selectRandomly="true">
       <flowStepCriteria name="traceCode" value="consumeExtFlowStepBegin" />
       <flowStepCriteria name="flowStepInterfaceName" value="{http://petals.ow2.org/}HelloWorldService" />
       <flowStepCriteria name="flowStepServiceName" value="{http://petals.ow2.org/}HelloWorldService" />
       <flowStepCriteria name="flowStepOperationName" value="{http://petals.ow2.org/}sayHello" />
       <flowStepInfo attribute="flowInstanceId" property="initial-flow-instance-id" />
       <flowStepInfo attribute="flowStepId" property="initial-flow.flow-step-id.rmi-consumer" />
    </petals-extract-flow-step-info>
  • Environment:
    -

Activity

Christophe DENEUX made changes - Fri, 15 Apr 2016 - 12:01:31 +0200
Field Original Value New Value
Priority Major [ 3 ]
Description When several flow steps match the given criteria, instead of using always the same flow (using parameter '{{row}}'), we should be able to select a flow step randomly:
{code:xml}
<petals-extract-flow-step-info refid="aggregated-flows" selectRandomly="true">
         <flowStepCriteria name="traceCode" value="consumeExtFlowStepBegin" />
         <flowStepCriteria name="flowStepInterfaceName" value="{http://petals.ow2.org/}HelloWorldService" />
         <flowStepCriteria name="flowStepServiceName" value="{http://petals.ow2.org/}HelloWorldService" />
         <flowStepCriteria name="flowStepOperationName" value="{http://petals.ow2.org/}sayHello" />
         <flowStepInfo attribute="flowInstanceId" property="initial-flow-instance-id" />
         <flowStepInfo attribute="flowStepId" property="initial-flow.flow-step-id.rmi-consumer" />
</petals-extract-flow-step-info>
{code}
When several flow steps match the given criteria, instead of using always the same flow (using parameter '{{row}}'), we should be able to select a flow step randomly:
{code:xml}
<petals-extract-flow-step-info refid="aggregated-flows" selectRandomly="true">
   <flowStepCriteria name="traceCode" value="consumeExtFlowStepBegin" />
   <flowStepCriteria name="flowStepInterfaceName" value="{http://petals.ow2.org/}HelloWorldService" />
   <flowStepCriteria name="flowStepServiceName" value="{http://petals.ow2.org/}HelloWorldService" />
   <flowStepCriteria name="flowStepOperationName" value="{http://petals.ow2.org/}sayHello" />
   <flowStepInfo attribute="flowInstanceId" property="initial-flow-instance-id" />
   <flowStepInfo attribute="flowStepId" property="initial-flow.flow-step-id.rmi-consumer" />
</petals-extract-flow-step-info>
{code}
Christophe DENEUX made changes - Fri, 15 Apr 2016 - 12:01:44 +0200
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Fri, 15 Apr 2016 - 12:01:49 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Mon, 18 Apr 2016 - 18:45:04 +0200

Added in trunk

Show
Christophe DENEUX added a comment - Mon, 18 Apr 2016 - 18:45:04 +0200 Added in trunk
Christophe DENEUX made changes - Mon, 18 Apr 2016 - 18:45:04 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 2.5.1 [ 10598 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
41s
1
Christophe DENEUX
Fri, 15 Apr 2016 - 12:01:44 +0200
Open Open In Progress In Progress
5s
1
Christophe DENEUX
Fri, 15 Apr 2016 - 12:01:49 +0200
In Progress In Progress Resolved Resolved
3d 6h 43m
1
Christophe DENEUX
Mon, 18 Apr 2016 - 18:45:04 +0200



People

Dates

  • Created:
    Fri, 15 Apr 2016 - 12:01:03 +0200
    Updated:
    Mon, 18 Apr 2016 - 18:45:04 +0200
    Resolved:
    Mon, 18 Apr 2016 - 18:45:04 +0200