You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/02/26 20:19:01 UTC

[jira] Updated: (TAP5-345) AjaxFormLoop should be able to deduce a default ValueEncoder from the type of its value parameter

     [ https://issues.apache.org/jira/browse/TAP5-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-345:
--------------------------------------

    Summary: AjaxFormLoop should be able to deduce a default ValueEncoder from the type of its value parameter  (was: AjaxFormLoop should be able to deduce a default PrimaryKeyEncoder from the type of its value parameter)

> AjaxFormLoop should be able to deduce a default ValueEncoder from the type of its value parameter
> -------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-345
>                 URL: https://issues.apache.org/jira/browse/TAP5-345
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>
> It should not be necessary to bind the encode parameter of AjaxFormLoop when iterating over (for example) Hibernate entities, as from the value parameter's type we should be able to identify the entity type and provide a PKE from that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.