manuel aldana schrieb:
So you mean if I provide a coercion for User, the User gets serialized
to an activation-context snippet in the URL, and after that the
snippets gets deserialized back to my User object?
I don't think that serialization is used. It's more that you pass those
values necessary to construct the object in question.
Maybe an out of the box coercion for custom types would be interesting
(to an ordered comma separated String list). Surely it will also show
up problems, especially if my User does not only include simple types
only (and object graph is more complicated).
I don't see the use case. In my opinion, it's not that often in real
life that you have to provide your own type coercions. And this kind of
"out of the box coercion for custom types" cries for too much problems.
Andy Pahne schrieb:
That's possible. Have a look at
http://tapestry.formos.com/nightly/tapestry5/tapestry-ioc/coerce.html
esp. the section "Contributing new Coercions"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
