Em Sat, 28 Nov 2009 12:04:19 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
Ok. Thanks for your quick answers. The problem was an URL rewriting rule
which messed up a few things. Sorry for the fuss.
No problem. :) URL rewriting is very interesting, but needs to be
implemented in a very car
Hi.
Ok. Thanks for your quick answers. The problem was an URL rewriting rule
which messed up a few things. Sorry for the fuss.
Br,
Timo Westkämper.
Thiago H. de Paula Figueiredo wrote:
Em Sat, 28 Nov 2009 11:56:44 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
Here is a simple test. Clickin
Em Sat, 28 Nov 2009 11:56:44 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
Here is a simple test. Clicking on submit will raise an error, because
param1 is null.
Have you tested it with an URL with an activation context value? I use
forms in pages that use the activation context to edit o
Hi.
Here is a simple test. Clicking on submit will raise an error, because
param1 is null.
I am sorry, but what do you mean by independent? Is the activation
context supplied with form submits or not?
Br,
Timo.
public class FormSubmit {
private String param1;
void onActivate(Stri
Em Sat, 28 Nov 2009 09:27:27 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
This is a Tapestry beginner's question :
When doing form submissions is the page's activation context submitted
and taken into account in the onActivate call or are activationContexts
only for navigational requests
Hi.
This is a Tapestry beginner's question :
When doing form submissions is the page's activation context submitted
and taken into account in the onActivate call or are activationContexts
only for navigational requests?
The documentation of Form doesn't mention onActivate :
http://tapestry.f