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

Posted to commits@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2013/10/08 15:47:41 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=13789221#comment-13789221 ] 

Thiago H. de Paula Figueiredo commented on TAP5-1624:
-----------------------------------------------------

Denis, is this still an issue? TAP5-1446 is already fixed. Do you still see a need for TypeCoercer coercion overrides?

> 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.1#6144)