Re: Scheduler processor - accessing

> Neil,
>   Why not create your task xpl, to take an additional id param. Now create
> a unique xpl for each task id e.g. Task1.xpl task2.xpl
>
> These xpls will use oxf:pipeline to call the main task.xpl
>
> Does this sound like what you want?
> -----------------------------------------------
> Ryan Puddephatt
> Connectivity Developer
> Fidessa LatentZero
> 1 Old Jewry
> London EC2R 8DN
> Office: +44 (0) 20 7105 1000
> Direct: +44 (0) 20 7105 1812
> Blackberry: +44 (0) 79 8539 2458
> Fax: +44 (0) 20 7105 1001
> Email: [hidden email]
> Web: http://www.latentzero.com
>
>
> ----- Original Message -----
> From: ncrofts <[hidden email]>
> To: [hidden email] <[hidden email]>
> Sent: Tue Dec 16 20:21:54 2008
> Subject: [ops-users]  Scheduler processor - accessing
>
>
> 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
> --
> View this message in context:
> http://www.nabble.com/Scheduler-processor---accessing-tp21040987p21040987.html
> Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.com.
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> _______________________________________________________________________
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by Verizon Business Internet
> Managed Scanning Services - powered by MessageLabs. For further
> information visit http://www.mci.com
>

> Neil,
>   Why not create your task xpl, to take an additional id param. Now
> create a unique xpl for each task id e.g. Task1.xpl task2.xpl
>
> These xpls will use oxf:pipeline to call the main task.xpl
>
> Does this sound like what you want?
> -----------------------------------------------
> Ryan Puddephatt
> Connectivity Developer
> Fidessa LatentZero
> 1 Old Jewry
> London EC2R 8DN
> Office: +44 (0) 20 7105 1000
> Direct: +44 (0) 20 7105 1812
> Blackberry: +44 (0) 79 8539 2458
> Fax: +44 (0) 20 7105 1001
> Email: [hidden email]
> Web: http://www.latentzero.com
>
>
> ----- Original Message -----
> From: ncrofts <[hidden email]>
> To: [hidden email] <[hidden email]>
> Sent: Tue Dec 16 20:21:54 2008
> Subject: [ops-users]  Scheduler processor - accessing
>
>
> 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
> --
> View this message in context:
> http://www.nabble.com/Scheduler-processor---accessing-tp21040987p21040
> 987.html Sent from the ObjectWeb OPS - Users mailing list archive at
> Nabble.com.
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
>
> ______________________________________________________________________
> _ The information transmitted is intended only for the person or
> entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or
> other use of, or taking of any action in reliance upon, this
> information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the
> sender and delete the material from any computer.
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by Verizon Business Internet
> Managed Scanning Services - powered by MessageLabs. For further
> information visit http://www.mci.com
>

> Ok, well if you know java you could rewrite the scheduler processor to add
> an additional input to the XPL (make it optional for backward
> compatibility) that passes the task id
>
> Ryan
>
> -----------------------------------------------
> Ryan Puddephatt
> Connectivity Consultant
> Fidessa LatentZero
> 1 Old Jewry
> London EC2R 8DN
> Office: +44 (0) 20 7105 1000
> Direct: +44 (0) 20 7105 1812
> Blackberry: +44 (0) 79 8539 2458
> Fax: +44 (0) 20 7105 1818
> Email: [hidden email]
> Web: http://www.latentzero.com
>
>
> -----Original Message-----
> From: Neil Crofts (Gmail) [mailto:[hidden email]]
> Sent: 17 December 2008 10:19
> To: [hidden email]
> Subject: [ops-users] Re: Re: Scheduler processor - accessing
>
> Ryan,
>
> Thanks for the suggestion. Unfortunately my requirement is such that over
> time I need to schedule thousands (in theory an infinite number) of task
> events. Each task needs to be able to identify what event has occurred, so
> that it can access the right data to process. I'd therefore need a unique
> pipeline for each, which is not really manageable for me.
>
> I was sort of hoping I'd be able to figure out which task was running to
> be able to connect the right data to the pipeline that is invoked. I'm
> wondering if I have misinterpreted how the scheduler was intended to be
> used?
>
> Regards,
> Neil
>
> --------------------------------------------------
> From: "Ryan Puddephatt" <[hidden email]>
> Sent: Tuesday, December 16, 2008 9:00 PM
> To: <[hidden email]>
> Subject: [ops-users] Re:  Scheduler processor - accessing
>
>> Neil,
>>   Why not create your task xpl, to take an additional id param. Now
>> create a unique xpl for each task id e.g. Task1.xpl task2.xpl
>>
>> These xpls will use oxf:pipeline to call the main task.xpl
>>
>> Does this sound like what you want?
>> -----------------------------------------------
>> Ryan Puddephatt
>> Connectivity Developer
>> Fidessa LatentZero
>> 1 Old Jewry
>> London EC2R 8DN
>> Office: +44 (0) 20 7105 1000
>> Direct: +44 (0) 20 7105 1812
>> Blackberry: +44 (0) 79 8539 2458
>> Fax: +44 (0) 20 7105 1001
>> Email: [hidden email]
>> Web: http://www.latentzero.com
>>
>>
>> ----- Original Message -----
>> From: ncrofts <[hidden email]>
>> To: [hidden email] <[hidden email]>
>> Sent: Tue Dec 16 20:21:54 2008
>> Subject: [ops-users]  Scheduler processor - accessing
>>
>>
>> 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
>> --
>> View this message in context:
>> http://www.nabble.com/Scheduler-processor---accessing-tp21040987p21040
>> 987.html Sent from the ObjectWeb OPS - Users mailing list archive at
>> Nabble.com.
>>
>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email
>> ______________________________________________________________________
>>
>> ______________________________________________________________________
>> _ The information transmitted is intended only for the person or
>> entity to which it is addressed and may contain confidential and/or
>> privileged material. Any review, retransmission, dissemination or
>> other use of, or taking of any action in reliance upon, this
>> information by persons or entities other than the intended recipient
>> is prohibited. If you received this in error, please contact the
>> sender and delete the material from any computer.
>>
>> _____________________________________________________________________
>> This e-mail has been scanned for viruses by Verizon Business Internet
>> Managed Scanning Services - powered by MessageLabs. For further
>> information visit http://www.mci.com
>>
>
>
>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
>
> _______________________________________________________________________
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
> _____________________________________________________________________
> This e-mail has been scanned for viruses by Verizon Business Internet
> Managed Scanning Services - powered by MessageLabs. For further
> information visit http://www.mci.com
>