> is returning a link in onSuccess the right way to build the URL If you're using @ActivationRequestParam then as Thiago said a void return is probably best. If you're not using @ActivationRequestParam you will either need to build a link or use @Persist (lets not discuss activation context here).
> you'll notice in onSuccess I'm getting the objects name and then passing > the string name Ah yeah... I can see that now. So it's using the String ValueEncoder not the hibernate ValueEncoder. > should I create some sort of encoder That's exactly what i'd do > should I do the work up front and store a column in the database I'd never store a value that can be calculated. It's unnecessary maintenance. I guess a question you want to ask yourself is should your custom encoder be global or just for these few selects? If it's global, you might want to consider overriding the default string ValueEncoder. -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-remove-query-parmeter-from-url-string-tp5716922p5717001.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
