[
https://issues.apache.org/jira/browse/TAPESTRY-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Westgate updated TAPESTRY-1598:
------------------------------------
Component/s: (was: tapestry-ioc)
> Trivial SelectModels (e.g. Lists of Integer objects) now require a
> ValueEncoder whereas before they "just worked".
> ------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1598
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1598
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Nick Westgate
> Priority: Minor
>
> (This could be considered an enhancement except that it worked in a previous
> snapshot.)
> Summary says it all but here's a simple example:
> html:
> <select t:type="select" t:value="someIntegerProperty"
> t:model="selectModelList"></select>
> java:
> public List getSelectModelList() // note list is currently broken as
> per TAPESTRY-1597
> {
> List<Integer> model = new ArrayList<Integer>();
> model.add(new Integer(1));
> model.add(new Integer(2));
> return model;
> }
> Now results in the following exception:
> org.apache.tapestry.ioc.internal.util.TapestryException
> No adapter from type java.lang.Integer to type
> org.apache.tapestry.services.ValueEncoderFactory is available (registered
> types are java.lang.Enum, java.lang.String).
> Defining ValueEncoders for all the simple wrapper types used in domain
> objects defeats the purpose of all the smart type conversion Tapestry does
> elsewhere.
> Cheers,
> Nick.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
