----- Original Message -----
From: "Kalle Korhonen" <kalle.o.korho...@gmail.com>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Tuesday, November 02, 2010 8:24 AM
Subject: Re: Let's make @ActivationRequestParameter first-class citizen
2010/11/2 Vjeran Marcinko <vjeran.marci...@email.t-com.hr>:
And finally, with 5.2. release, we got @ActivationRequestParameter
annotation, and I felt relieved. Finally!
But, to spoil the celebration, I noticed immediately there is no way to
specify whether query parameter is required, so I had to place manual
check
of all these parameters inside onActivate() method. Not to mention that
in
some pages I didn't even have this onActivate() method since I didn't
need
it, but now I had to introduce it.
I reported the improvement issue here:
https://issues.apache.org/jira/browse/TAP5-1290
What should happen if an argument is required but not given? Just
asking, might not be that simple to decide on common logic.
Well, maybe it's just me, but I don't see any problem with default tapestry
exception page reporting that required parameter is not present in URL query
part.
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
