You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/12/24 02:38:15 UTC

[jira] [Commented] (TAP5-1624) Add support for overriding default TypeCoercer's coercions

    [ https://issues.apache.org/jira/browse/TAP5-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257804#comment-14257804 ] 

Howard M. Lewis Ship commented on TAP5-1624:
--------------------------------------------

This is on my list of "if I was starting from scratch" ... there would just be OrderedConfigurations and MappedConfigurations, so there would always be a way to override.

> Add support for overriding default TypeCoercer's coercions
> ----------------------------------------------------------
>
>                 Key: TAP5-1624
>                 URL: https://issues.apache.org/jira/browse/TAP5-1624
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Denis Stepanov
>
> Right now it is imposible to implement TAP5-1446 without changes in Tapestry.
> It will probably require to add new service TypeCoercerOverride, TyprCoercerImpl will use it to override all tuples with equal sourceType and targetType.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)