it?
Is it another bug in javaflow?
In the current implementation the flow object is stored into the
session. So after the first initialization of foo to true, you
will get the value true for all called continuations from the same
browser.
member variables have the scope of the seesion.
local variable
Stephan Michels wrote:
member variables have the scope of the seesion.
Ok. But makes this sense? If I have no continuation I need no member
variable.
Isn't it better to remove the member vars from the session scope and
bind them on the contonuation object?
What's the reason to bind member
Stephan Coboos wrote:
Stephan Michels wrote:
member variables have the scope of the seesion.
Ok. But makes this sense? If I have no continuation I need no member
variable.
Isn't it better to remove the member vars from the session scope and
bind them on the contonuation object?
What's the
Stephan Coboos wrote:
Stephan Michels wrote:
member variables have the scope of the seesion.
Ok. But makes this sense? If I have no continuation I need no member
variable.
Isn't it better to remove the member vars from the session scope and
bind them on the contonuation object?
What's the
. There is no initialization process! So foo is always
true in the same browser instance. In my opinion, If I make a reload
without a call of a continuation the var reload should be false, should it?
Is it another bug in javaflow?
Thank you for your help.
Regards
Stephan
