tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-98) Tapestry should be smarter about coersing string literals to Enum's
Date Sat, 02 Apr 2011 01:24:05 GMT

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

Howard M. Lewis Ship commented on TAP5-98:

Tricky to do this in a way that is both thread safe, and will not cause memory leaks if the
Enum type is loaded from a reloadable class loader.

> Tapestry should be smarter about coersing string literals to Enum's
> -------------------------------------------------------------------
>                 Key: TAP5-98
>                 URL: https://issues.apache.org/jira/browse/TAP5-98
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Alexander Gavrilov
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
> In the current implementation to allow coersion form string literal to Enum we need to
add contribution to the TypeCoercer. This is working. But this coersion can be performed by
default using just Enum.valueOf (Class, String), so there are not required to register new
coersion for every used enum type. In this case whe are lost the case insensibility of enum
coersions, but if this is meaningfull for everyone we can still use contributed coersions,
and if no one is found fallback do the default. Enum.valueOf

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message