To be clear; if there isn't a specific ValueEncoder for your object type, then Tapestry will use a pair of TypeCoercers (your object type -> String, and String -> your object type). ValueEncoder (which should really be named ValueTranscoder) is a single object that handles both directions, and is expressly oriented for encoding data into a client-side String (whether that string will be stored into the URL, a hidden form field, or a cookie).
Beware of relying on Serializable; that's really intended for prototyping only, as serializing even a simple object can result in a huge string, and often unintentionally drags in a large object graph. Generally speaking, when we see complaints about Tapestry rendering slowly (either on the server or on the client), it's because they've stumbled over this. On Thu, May 31, 2012 at 6:05 AM, Lance Java <[email protected]> wrote: > You will need to imlpement a ValueEncoder and contribute it to the > ValueEncoderSource. > > http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/ValueEncoder.html > http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/ValueEncoderSource.html > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/activation-context-in-Tapestry-tp5713555p5713557.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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]
