I would like to clarify the objective of this task:

- Introduce the concept of a Task provider in to ESB. Which means any
existing task (task config) can be ran on the available task provider( this
can be ntask, quartz or anything)
- However, the recipes concept is completely transparent at Synapse level.
Simply we don't have to thing about recipes when doing this. Recipe(or
Dish) can be consider as a place where specific logic is executed on top of
generic task.
- All the details on sequence deployment, template invocation is not
related to ESB task provider concept.


On Sat, Mar 22, 2014 at 7:36 AM, Ishan Jayawardena <[email protected]> wrote:

> I am working on $subject to support scheduled invocation of recipes in the
> ESB. This mainly includes replacing the existing quartz based task
> scheduler with ntask scheduler. The new task type is based on ntask, and it
> will be added as a new component in the mediation category. We can use the
> existing task management UI of the ESB to add and manage tasks.
>
> In addition to the task schedule information, template name and template
> parameter values, a special property must be added to the task parameter
> list at the time of task creation so that the task can invoke the template
> within its execute method.
>
> The task,
>      reads properties and builds a synapse sequence by inserting the
> recipe template in it,
>      deploys the sequence into synapse,
>      injects a message to the above sequence to invoke the template.
>
> Thanks,
> Ishan.
>
> --
> Ishan Jayawardena
> Senior Software Engineer
> Mobile: +94 (77) 408 2330
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to