This was addressed in 5.2 or 5.3, where Link has a new method, addParameterValue(String, Object). And yes, its a ValueEncoder under the covers.
On Fri, Apr 1, 2011 at 10:18 PM, Robert Zeigler <[email protected]> wrote: > Is there some specific reason why addParameter is (String,String) rather than > (String,Object)? Couldn't PageRenderLinkSource use ValueEncoderSource to > encode the provided object to string automatically? > > Just thinking. > > Or maybe we keep the current implementation so a user can provide an exact > string if they want absolute control over what shows up in the URL, as well > as an addParameter(String,Object)? > > Anyway, I was thinking of adding the new method, but I wanted to check in on > what the original rationale for String, String was first. > > Robert > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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]
