This is exactly related to comment I left on TAP-1190 so I'll repeat the
question here -
Why doesn't @QueryParameterMapped has attribute to specify whether it is
required or optional? In my web apps I don't use onActivate/onPassivate for
anything else beside setting/getting activation context fields, and I don't
care whether these fields are passed in URLs throguh path info or URL query
params, so I'll probably end up using only @QueryParameterMapped since it is
more powerful way to pass page render parameters (parameter can be named and
optional versus activate/passivate way) and sometimes I want these to be
required (as it is now I understand they are always optional, so I want to
save myself having to null check every time before I prepare my model with
it).
-Vjeran
----- Original Message -----
From: "Howard Lewis Ship" <hls...@gmail.com>
Newsgroups: gmane.comp.java.tapestry.user
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Sunday, June 27, 2010 12:18 AM
Subject: Re: [Tapestry Central] Tapestry 5.2: Improved Query Parameter
Support
On Sat, Jun 26, 2010 at 2:55 PM, Josh Canfield <joshcanfi...@gmail.com>
wrote:
@QueryParameter --> @RequestParameter
@QueryParameterMapped --> @ActivationQueryParameter
I'd like to hear more about how these are going to be different, other
than were they are located. What parameters are needed in one case but not
the other? Could that be achieved with a secondary related annotation?
For @QueryParameter, the name attribute is required. It is optional
for @QueryParameterMapped (because we can use the field name as a
default). @QueryParameter has an attribute for required vs. optional.
@QueryParaterMapped may added attributes to control whether the value
is encoded for event requests links or for page request links.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
