Re: [Components] Thoughts about components for cronjobs
On Thu, Sep 16, 2010 at 10:32 PM, Xiongjie Chen x...@ez.no wrote: Hello everyone, Today I discussed with some partner developers about one topic. We got the feeling that cronjob is not so easy to configure(especially there are many tasks), manage (monitor, control). Then I thought a little bit how to improve this, it should be great if there are some components in zeta components for this. Also I think this is good and general need for 'enterprise use'. I also found this one: http://pear.php.net/package/System_Daemon/docs but it's just a daemon, which is not enough. Ideally there should be a tool/possibility to configure task, control task, monitor task/memory use, etc. Any idea on this or there is already some existence but I didn't know? Why would PHP do a better job than Bash at this system administration job? Regards James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey. -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
[Components] Workflow - suspend - saveToVariableHandlers - doSuspend
On the suspend method in ezcWorkflowExecution doSuspend is called after saveToVariableHandlers() but in the commentary says diferent This method calls doSuspend() before calling saveToVariableHandlers()... I had a problem with commits that got resolved when I changed the saveToVariableHandlers to be executed after doSuspend. Is ther any problem in executing doSuspend first and saveToVariableHandlers after? -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
[Components] Supend workflow until condition is true
Hi, I', trying to make a workflow in wich, after some user input the workflow follows on or stays in the same node until a certain form field matches a condition I've created and Input node, after that I have a ExclusiveChoise with forks to a ServiceObjectClass if the condition is false or to a SimpleMerge node if the condition is true The ServiceObjectClass will suspend the workflow, and that is working OK, but the data is the execution_waiting_for field is lost, and the workflow will never go the right path if the condition later on turn true. I don't know if i'm doing the right workflow, or if I have to do something to keep the original state of the input node. So in a glance the idea is: Input node (id: 1) - ExclusiveChoise (id: 2) -True? - SimpleMerge (id: 3)) - End -False? - ServiceObjectClass (id: 4) - SimpleMerge (id: 3)) - End node 4 suspends the workflow and it should be back to node 1 so the user later on can change the input value so condition is true Thanks -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
