It's not very intuitive. If you got 2 annotations, named @QueryParameter and @RequestParamter, you couldn't possibly know who does what without reading the docs.
If I understand this correctly, @QueryParameter is for passing a query string param as context to a component event handler, while QueryParameterMapped contributes to page activation. Why not: @QueryComponentEventParameter @QueryPageActivationContext Or something similar. If possible, the name should say what it actually does, not only where it gets its data from (query string). I see the point here with avoiding too long names, though... Inge On Sat, Jun 26, 2010 at 5:36 PM, Michael Gentry <mgen...@masslight.net>wrote: > Maybe @RequestParameter? I don't think that is in use. > > Thanks, > > mrg > > > On Sat, Jun 26, 2010 at 11:32 AM, Howard Lewis Ship <hls...@gmail.com> > wrote: > > It's still alpha, and changeable, if a consensus can be reached. > > > > On Sat, Jun 26, 2010 at 8:29 AM, Michael Gentry <mgen...@masslight.net> > wrote: > >> LinkParameter? HTTPParameter (a lot of P's in that one)? > >> URLParameter? ... :-) > >> > >> mrg > >> > >> > >> On Sat, Jun 26, 2010 at 6:02 AM, Igor Drobiazko > >> <igor.drobia...@gmail.com> wrote: > >>> @QueryParameter does already exists (since 5.2). It is used to annotate > a > >>> parameter of an event handler method. > >>> > >>> On Sat, Jun 26, 2010 at 8:19 AM, Geoff Callender < > >>> geoff.callender.jumpst...@gmail.com> wrote: > >>> > >>>> Good stuff. > >>>> > >>>> One question, though - why such a long name, @QueryParameterMapped, > instead > >>>> of just @QueryParameter? > >>>> > >>>> On 25/06/2010, at 12:00 PM, Howard wrote: > >>>> > >>>> > I just checked in some very nice changes for Tapestry 5.2; you can > now > >>>> > easily store data about a page in the URL as query parameters: > >>>> > @QueryParameterMapped private String name; > >>>> > > >>>> > By annotating a page (not a component!) field this way, the field > will > >>>> > be mapped to the query parameter "name". When a page render link or > >>>> > component event link for the page is created, the current value of > the > >>>> > field will be added as parameter "name". When that link is triggered > to > >>>> > form a request, the parameter will be read and the field updated > from > >>>> > the query parameter value. > >>>> > It isn't limited to strings ... it uses the whole ValueEncoder > >>>> > machinery so that you can encode numbers or even Hibernate entities > >>>> > (represented in the URL as their primary key). > >>>> > Cool stuff, if I do say so myself. Even I'm still learning how to > flex > >>>> > the massive amount of meta-programming muscle that Tapestry > provides. > >>>> > It turns out that the combination of component method advice with > >>>> > custom events triggered on the page can do some really sophisticated > >>>> > things! > >>>> > > >>>> > -- > >>>> > Posted By Howard to Tapestry Central at 6/24/2010 07:00:00 PM > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >>>> For additional commands, e-mail: users-h...@tapestry.apache.org > >>>> > >>>> > >>> > >>> > >>> -- > >>> Best regards, > >>> > >>> Igor Drobiazko > >>> http://tapestry5.de > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > >> For additional commands, e-mail: users-h...@tapestry.apache.org > >> > >> > > > > > > > > -- > > Howard M. Lewis Ship > > > > Creator of Apache Tapestry > > > > The source for Tapestry training, mentoring and support. Contact me to > > learn how I can get you up and productive in Tapestry fast! > > > > (971) 678-5210 > > http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
