And, BTW, once I get all the new class transformation APIs settled out, it will be easy to add the logic to inject an event handler method with a query parameter rather than event context.
On Sat, Feb 13, 2010 at 2:24 PM, Dan Adams (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TAP5-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833468#action_12833468 > ] > > Dan Adams commented on TAP5-928: > -------------------------------- > > there are legit application scenarios where using query parameters is the > most natural fit for maintaining page state / page context. > > i propose that we change Link.addParameter() to not throw > IllegalArgumentException if called multiple times with the same value. this > should be backward compatible since we are relaxing restrictions on it. > >> Link should support multiple values for a single query parameter >> ---------------------------------------------------------------- >> >> Key: TAP5-928 >> URL: https://issues.apache.org/jira/browse/TAP5-928 >> Project: Tapestry 5 >> Issue Type: Improvement >> Components: tapestry-core >> Affects Versions: 5.1.0.5 >> Reporter: Dan Adams >> >> You should be able to set multiple values for a query parameter in the same >> way that you can get multiple values for a single parameter from Request. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- 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: [email protected] For additional commands, e-mail: [email protected]
