On Wed, Apr 7, 2010 at 6:43 AM, kiko <[email protected]> wrote:
> Hi, I can't figure out the process syntax to also use this sub_wfid
> pattern.
>
> I used to use this:
> set :f => 'args', :value => "--filter ${f:filter} --filter_seq
> ${f:__ip__}"
>
> I looked here and didn't see any documentation on the reserved or
> special fields, does this documentation exists some where, or more
> information about the workitem object.
>
> http://ruote.rubyforge.org/dollar.html
Hello,
you can do
set :f => 'args', :value => '--filter ${f:filter} --filter_seq ${sub_wfid}'
Note that ruote 2.1 allows you to write
set 'args' => '--filter ${f:filter} --filter_seq ${sub_wfid}'
I will enhance the dollar.html page you've been referencing. Thanks
for pointing out the lack.
> I also want to find how out
> how to get more error information from the wfe, currently it clunky
> for me to always look at the error logs, I'd like to dump the errors
> to console as well.
There are a few techniques available.
At first you could place a final "-d" when invoking your Ruby + ruote
application. It will be detected by the worker upon errors and cause
it to spit the message to the console as well :
http://github.com/jmettraux/ruote/blob/ruote2.1/lib/ruote/worker.rb#L102-118
If you want to see what the worker is actually doing, you can turn the
"noisy" mode on :
engine.context.logger.noisy = true
It will let the worker detail its activity like in :
---8<---
0 00 la * 20100407-yadariyu {:t=>["define", {"name"=>"test"},
[["sequence", {}, [["echo", {"a"=>nil}, []], ["echo", {"b"=>nil},
[]]]]]], :wi=>["0!!20100407-yadariyu", 0]}
1 00 ap * 20100407-yadariyu 0_0 {:pi=>"0!!20100407-yadariyu",
:t=>["sequence", {}, [["echo", {"a"=>nil}, []], ["echo", {"b"=>nil},
[]]]], :wi=>["0_0!!20100407-yadariyu", 0]}
2 00 ap * 20100407-yadariyu 0_0_0
{:pi=>"0_0!!20100407-yadariyu", :t=>["echo", {"a"=>nil}, []],
:wi=>["0_0_0!!20100407-yadariyu", 0]}
3 00 re * 20100407-yadariyu 0_0 {"updated_tree"=>nil,
:wi=>["0_0_0!!20100407-yadariyu", 0]}
4 00 ap * 20100407-yadariyu 0_0_1
{:pi=>"0_0!!20100407-yadariyu", :t=>["echo", {"b"=>nil}, []],
:wi=>["0_0_1!!20100407-yadariyu", 0]}
5 00 re * 20100407-yadariyu 0_0 {"updated_tree"=>nil,
:wi=>["0_0!!20100407-yadariyu", 0]}
6 00 re * 20100407-yadariyu 0 {"updated_tree"=>nil,
:wi=>["0_0!!20100407-yadariyu", 0]}
7 00 te * 20100407-yadariyu 0 {:wi=>["0_0!!20100407-yadariyu", 0]}
--->8---
In a regular *nix terminal, that output is coloured.
In an upcoming version of ruote, I will probably add specific hooks
for errors, so that when they appear, an email is sent, or a file is
written, ...
Please also have a look at how ruote is tested, it will help you test
your own processes.
http://github.com/jmettraux/ruote/tree/ruote2.1/test/functional/
On that front, there is also a ruote-cukes which leverages Cucumber
(http://cukes.info/) to test ruote process definitions :
http://github.com/jmettraux/ruote-cukes
Best regards, thanks again,
--
John Mettraux - http://jmettraux.wordpress.com
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
To unsubscribe, reply using "remove me" as the subject.
