Hi,
I have some questions about the scheduler processor:
* What's happening when synchronized is set to false and another
task with the same name is already running?
* Is the previous instance of the task stopped or can several
instances of a same task run at the same time?
* What's happening when an exception is raised in a task?
* Is this exception handling configurable?
* Why are the inputs of the task embedded in the config input?
Wouldn't that make more sense to define them as... inputs?
* Is that an error to try to stop a task that isn't running?
* What happens exactly when a command is stopped?
* Are there any risk that a task is stopped in the middle of a
processing?
* If yes, shouldn't it be possible to define transaction like
sections in a pipeline which should be completed before a task
can be stopped?
* Wouldn't it be fine if the scheduler processor had a third
command that outputs the list of running tasks?
Thanks,
Eric
--
Curious about Relax NG? Read my book online.
http://books.xmlschemata.org/relaxng/
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
