Excellent André,
Glad you found an alternate way than trying to replay requests which would be
brittle if you could get it to work. Your new way is much better with the
lambdas. It’s basically blocks (like in Smalltalk) that you can execute when
you want. Javascript does this quite a bit to wi
Hi Aaron,
Thank you for your reply. That is a nice idea. At the end I have solved
it with Lambdas. The action on (3) contains not only a pageWithName(),
it initializes also the new component by calling some public method. So
I moved that stuff into a Lambda and store it within a class member
Hi André,
At step 3 can you store a variable that remembers the page the user intends to
go to?
maybe you can make an enum with all the possible pages they could go to on the
next step and the variable would be one of those values.
Then, in 7b, you can reference that variable and create the
Hi Aaron,
Thank you for your answer. Here the more detailled workflow:
1. User goes to page A.
2. User clicks there on an element which submits the HTML
form and should show i.e. page B later (there are a
lot of possible things the user can do on page A which
submit the form and forward
Hi André,
I didn’t fully understand but it sounds like maybe you are working too hard.
It’s easier to hold onto WOComponents than it is to hold onto contexts. If you
have an “old page” hold onto it and just return the page. If you don’t have the
outermost page you can find that quickly by doing
Hi,
I try to replay an old WORequest after some other
request/response-loops, but I don't know, how it could work.
My application validates some values after the user clickes somewhere on
a page. In the validation routine I don't know, which action the user
has executed exactly. But the vali