set expression

[rebo]

I'm a bit confused about the set expression, I am trying to set a
workitem field so a latter participant can access it.

For instance, from the documentation:

sequence do
set :field => 'subject', :value => 'food and beverage'
set :field => 'date', :val => 'tomorrow'
participant :ref => 'attendees'
end

However putting the above in ruote-kit and launching the process does
not seem to affect the subsequent workitem's fields for attendess.

I get the same issue with the set expression within my own process
definitions.

[Torsten Schönebaum]

Am Donnerstag, den 06.01.2011, 08:18 -0800 schrieb rebo:
> I'm a bit confused about the set expression, I am trying to set a
> workitem field so a latter participant can access it.
>
> For instance, from the documentation:
>
> sequence do
> set :field => 'subject', :value => 'food and beverage'
> set :field => 'date', :val => 'tomorrow'
> participant :ref => 'attendees'
> end
>
> However putting the above in ruote-kit and launching the process does
> not seem to affect the subsequent workitem's fields for attendess.

I can't reproduce this problem here[1]. Which versions of ruote,
ruote-kit and Ruby do you use? Mine are:
ruote: 2.1.11
ruote-kit: current HEAD
Ruby: ruby 1.8.7 (2010-04-19 patchlevel 253) [i686-linux], MBARI 0x8770,
Ruby Enterprise Edition 2010.02

Cheers,
Torsten

[1] That means, the workitem fields appear in
http://localhost:9292/_ruote/workitems/0_0_2!!20110106-bejoyarani
(example url) as expected.

[rebo]

Hmm something strange is going on, when I run ruote-kit independently
via rackup, it works fine. But when running as a gem running from my
rails app it doesn't work. Will investigate further.

On Jan 6, 4:31 pm, Torsten Schönebaum <torsten.schoeneb...@web.de>
wrote:

[Torsten Schönebaum]

rebo wrote:
> Hmm something strange is going on, when I run ruote-kit independently
> via rackup, it works fine. But when running as a gem running from my
> rails app it doesn't work. Will investigate further.

Is there a workitem for attendees? If not, it's likely that you're not
running a ruote worker in your rails app.

HTH,
Torsten

[rebo]

Hi thanks for the advice Torsten but i think i've found the cause ( or
at least a trigger) of the problem.

The route setup was fine, ruote worker running in seperate process no
problem.

What seems to cause the issue is when I have

gem 'sinatra', '1.0'

within my gemfile, commenting out that line everything runs fine. Put
it back in and set expressions do not work. Its really strange as
within Ruote-kit itself that sinatra version is specified.

Very odd!

On Jan 7, 11:39 am, Torsten Schönebaum <torsten.schoeneb...@web.de>
wrote:

[John Mettraux]

On Fri, Jan 07, 2011 at 04:25:25AM -0800, rebo wrote:
>
> Hi thanks for the advice Torsten but i think i've found the cause ( or
> at least a trigger) of the problem.
>
> The route setup was fine, ruote worker running in seperate process no
> problem.
>
> What seems to cause the issue is when I have
>
> gem 'sinatra', '1.0'
>
> within my gemfile, commenting out that line everything runs fine. Put
> it back in and set expressions do not work. Its really strange as
> within Ruote-kit itself that sinatra version is specified.
>
> Very odd!

Hello Rebo,

maybe Sinatra's set is shadowing ruote's set, since you can do

---8<---
require 'sinatra'

set :port, 3333

get '/' do
"nada"
end
--->8---

Best regards,

--
John Mettraux - http://jmettraux.wordpress.com

[rebo]

Must be something to do with that, as changing

class SetExpression < FlowExpression
names :set, :unset

to

class SetExpression < FlowExpression
names :setf, :unset

within fe_set.rb works with or without the sinatra gem in the
gemfile. (obviously using setf instead of set.) So some kind of
conflict on the set method....

[John Mettraux]

On Fri, Jan 07, 2011 at 04:50:07AM -0800, rebo wrote:
>
> Must be something to do with that, as changing
>
> class SetExpression < FlowExpression
> names :set, :unset
>
> to
>
> class SetExpression < FlowExpression
> names :setf, :unset
>
> within fe_set.rb works with or without the sinatra gem in the
> gemfile. (obviously using setf instead of set.) So some kind of
> conflict on the set method....

Hello,

I went on an added an 'rset' alias for the set expression :

https://github.com/jmettraux/ruote/commit/801afe5c932c7b1e176f9e2a62d0546c79e09d14

Went for 'r[uote]set' and not 'setf' since set can set variables and fields.

Many thanks !

[Torsten Schönebaum]

Nonetheless, sinatra's set shouldn't pollute the global namespace in
ruote-kit. I'll investigate that as soon as I've time for that.

Thanks for the report, rebo, and thanks for the workaround, John!

Cheers,
Torsten

[Torsten Schönebaum]

There's a fix in
https://github.com/tosch/ruote-kit/commit/00381b3ebe774fc37af0eae99bc6f149e1d51618

@rebo: Could you test if you may use 'set' in process definitions with
that fix?

Thanks again for the report,
Torsten