[xwiki-devs] [Contrib] xwiki-task-executor
Hi, while working on a project I developed this simple system for managing the execution of long running execute-once tasks. It uses the scheduler and it provides a nice framework for logging and error reporting. The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too long or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job. You can think of this system as a task queue that is processed in the background. I am contributing it to xwiki contrib. Thanks, Fabio
Which is pretty muych what job module is already. See http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing the execution of long running execute-once tasks. It uses the scheduler and it provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too long or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Yep. Job Module is cleaner of course but it's since 4.0M1... which rule out some older installation of XWiki. Good to know though (I didn't know about it) Thanks, -Fabio On Sat, Nov 10, 2012 at 1:14 PM, Thomas Mortagne <[email protected]>wrote:
Which is pretty muych what job module is already.
See http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module
On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing the execution of long running execute-once tasks. It uses the scheduler and it provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too long or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 11/10/2012 05:38 PM, Fabio Mancinelli wrote:
Yep.
Job Module is cleaner of course but it's since 4.0M1... which rule out some older installation of XWiki.
I think there's a difference in that the task executor module seems to provide a wiki integration (by that I mean the end-user of it just has to set up some XWiki objects in documents) while the job module is more an API ? Is that right ? Jerome
Good to know though (I didn't know about it)
Thanks, -Fabio
On Sat, Nov 10, 2012 at 1:14 PM, Thomas Mortagne <[email protected]>wrote:
Which is pretty muych what job module is already.
See http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module
On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing the execution of long running execute-once tasks. It uses the scheduler and it provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too long or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Yes. task executor is integrated with the wiki (it provides some UI for managing tasks, executors and, moreover, logs). It could have been implemented more easily if the JobModule API was available :) Anyway task-executor is installable on XWikis as old as 3.1. -Fabio On Sat, Nov 10, 2012 at 5:40 PM, Jerome Velociter <[email protected]>wrote:
On 11/10/2012 05:38 PM, Fabio Mancinelli wrote:
Yep.
Job Module is cleaner of course but it's since 4.0M1... which rule out some older installation of XWiki.
I think there's a difference in that the task executor module seems to provide a wiki integration (by that I mean the end-user of it just has to set up some XWiki objects in documents) while the job module is more an API ? Is that right ?
Jerome
Good to know though (I didn't know about it)
Thanks, -Fabio
On Sat, Nov 10, 2012 at 1:14 PM, Thomas Mortagne <[email protected]>**wrote:
Which is pretty muych what job module is already.
On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing
the
execution of long running execute-once tasks. It uses the scheduler and
it
provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too
long
or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
-- Thomas Mortagne ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________
devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
On Sat, Nov 10, 2012 at 5:40 PM, Jerome Velociter <[email protected]>wrote:
On 11/10/2012 05:38 PM, Fabio Mancinelli wrote:
Yep.
Job Module is cleaner of course but it's since 4.0M1... which rule out some older installation of XWiki.
I think there's a difference in that the task executor module seems to provide a wiki integration (by that I mean the end-user of it just has to set up some XWiki objects in documents) while the job module is more an API ? Is that right ?
This is not really a difference. The exact same way you can add new macros or components you could add wiki jobs. It's like saying wiki macros and java macros are two different concepts.
Jerome
Good to know though (I didn't know about it)
Thanks, -Fabio
On Sat, Nov 10, 2012 at 1:14 PM, Thomas Mortagne <[email protected]>**wrote:
Which is pretty muych what job module is already.
On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing
the
execution of long running execute-once tasks. It uses the scheduler and
it
provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too
long
or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
-- Thomas Mortagne ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________
devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
-- Thomas Mortagne
On 11/10/2012 05:55 PM, Thomas Mortagne wrote:
On Sat, Nov 10, 2012 at 5:40 PM, Jerome Velociter <[email protected]>wrote:
On 11/10/2012 05:38 PM, Fabio Mancinelli wrote:
Yep.
Job Module is cleaner of course but it's since 4.0M1... which rule out some older installation of XWiki.
I think there's a difference in that the task executor module seems to provide a wiki integration (by that I mean the end-user of it just has to set up some XWiki objects in documents) while the job module is more an API ? Is that right ?
This is not really a difference. The exact same way you can add new macros or components you could add wiki jobs.
Yes, *could*. Everyting is always possible :) I was pointing out the _current_ difference Jerome
It's like saying wiki macros and java macros are two different concepts.
Jerome
Good to know though (I didn't know about it)
Thanks, -Fabio
On Sat, Nov 10, 2012 at 1:14 PM, Thomas Mortagne <[email protected]>**wrote:
Which is pretty muych what job module is already.
On Sat, Nov 10, 2012 at 12:36 AM, Fabio Mancinelli < [email protected]> wrote:
Hi,
while working on a project I developed this simple system for managing
the
execution of long running execute-once tasks. It uses the scheduler and
it
provides a nice framework for logging and error reporting.
The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too
long
or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job.
You can think of this system as a task queue that is processed in the background.
I am contributing it to xwiki contrib.
Thanks, Fabio ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
-- Thomas Mortagne ______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
______________________________**_________________ devs mailing list [email protected] http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs>
participants (3)
-
Fabio Mancinelli -
Jerome Velociter -
Thomas Mortagne