On Fri, Apr 10, 2009 at 3:11 PM, harshal <[email protected]> wrote:
>
> A couple of concerns however are -
>
> * Is it like a macro expansion? If yes, in future, will it affect hot
> deployment or online changes in the process definitions?
Hello Harshal,
The first technique exposed (_eval) is not like macro expansion.
Expansion occurs at runtime.
The second technique is like macro expansion (it's tedious, that's why
I'm thinking about providing an "insert" pseudo-expression or
something like that).
Regarding "online changes" (in-flight modifications), the first
technique will display you the "_eval" expression before it gets
reached and after, you'll see the process instance with an updated
process definition.
For the second technique, since the insertion got performed at
definition time, the visible process definition will always be the
same.
"Hot deployment" : what is this ? I guess that if you do something
like "engine.launch('http://example.org/definition1.rb')" you have hot
deployment, out of the box.
> * Do you already know any side-effect of using '_eval' or any
> recommended way of using it elsewhere?
_eval is disabled by default since it's a bit dangerous : it's very
easy to request the evaluation of a piece of broken process.
> From website, I could know only about Ruby embedded in XML.
Understood, but if you look carefully at the example on the website,
you will notice that the inserted code is Ruby while the main process
is XML :
http://openwferu.rubyforge.org/expressions.html#exp_eval
Also, note that this expression is for advanced users and most users
are happy with classical subprocesses.
Best regards,
--
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
-~----------~----~----~----~------~----~------~--~---
