I believe this was added back in 2007...
Uli
Chris Lewis schrieb:
Wow. Is that recent behavior? I've not been aware of the default* method
convention before. Interesting indeed. Thanks for that!
Ulrich Stärk wrote:
IIRC from browsing through the source code this is done automagically
by type coercing from your type to String
(TypeCoercedValueEncoderFactory or something). The correspondig
Encoder is selected by the Select components defaultEncoder() method,
when no encoder parameter is provided (see the "Computed Parameter
Binding Defaults" section at
http://tapestry.apache.org/tapestry5/guide/parameters.html).
Cheers,
Uli
Chris Lewis schrieb:
I am, but that's not my question. My question is how does the select
component get a default value encoder when one is not provided as a
parameter? The source suggests it comes from the ValueEncoderSource
service, to which modules like tapestry-hibernate contribute. But
nowhere in the select's source does the it access the
ValueEncoderSource service. So, where/when/how does a default encoder
get set?
Thiago H. de Paula Figueiredo wrote:
Em Mon, 19 Jan 2009 13:54:11 -0300, Chris Lewis
<chris_le...@bellsouth.net> escreveu:
Hi list,
Hi!
I simply want to know how the Select component gets its encoder
from the ValueEncoderSource service, when an encoder isn't
explicitly provided as a parameter. Thanks!
Are you using tapestry-hibernate? If yes, it provides ValueEncoder's
using Hibernate's ClassMetaData class.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
