Scheduler processor - accessing unique task data

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Scheduler processor - accessing unique task data

ncrofts
Hi,

I was hoping to be able to use the oxf:scheduler processor to schedule several different tasks at different times, but then when the specified pipeline is invoked I would like to be able to identify which task has been invoked. In order to do this I was hoping to be able to access some piece of information in the invoked pipeline to be able to the figure out which data I need to process at that time.

As such I was wondering if there was any way to pass a unique id to the scheduler processor about which task has been set up. For example, I could generate a unique task name, but can't see how I would be able to access this from the pipeline that is invoked by the scheduler.

I also wondered if I could generate a unique pipeline name and then use wildcards to identify the instance of the task, but my understanding is that the pipeline invoked by the scheduler will not go throw the page-flow.

I could well be wrong on my understanding of these, or someone may be able to suggest a better stratgey, so any suggestions on how to approach this would be appreciated.

Thanks,
Neil