So.. does that mean that Coercion is deprecated, and we have to redo our
Coercions to be ValueEncoders instead?
what does this commit mean for people..
(though I think I agree with the change, just trying to tease out what I
have to do to deal with the change..)
Howard M. Lewis Ship (JIRA) wrote:
[
https://issues.apache.org/jira/browse/TAPESTRY-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2112.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.10
Came out nicely, a follow on will be to add automatic value encoding for
Hibernate entities (to tapestry-hibernate).
Tapestry should use ValueEncoders, not simple type coercion, to convert between
event context values, URL strings, and event method handler parameters
------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TAPESTRY-2112
URL: https://issues.apache.org/jira/browse/TAPESTRY-2112
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Reporter: Howard M. Lewis Ship
Assignee: Howard M. Lewis Ship
Fix For: 5.0.10
Currently (5.0.10-SNAPSHOT), Tapestry uses the TypeCoercer to convert such
values, such as when building an event context or a page activation context.
We need a service to which we can contribute ValueEncoders that can be used
instead of TypeCoercer.
This will open up a lot of possibilities in terms of automatically converting
Hibernate entities to primary keys and back.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
