[
https://issues.apache.org/jira/browse/TAP5-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672455#action_12672455
]
Howard M. Lewis Ship commented on TAP5-165:
-------------------------------------------
This is coming along well, but I'm having trouble with the automatic coercion
from PrimaryKeyEncoder to ValueEncoder. The problem is using reflection to dig
out the key type, which is very necessary.
> Components which use PrimaryKeyEncoder should be changed to use ValueEncoder,
> and PrimaryKeyEncoder should be eliminated.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-165
> URL: https://issues.apache.org/jira/browse/TAP5-165
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.16
> Environment: any
> Reporter: Robert Zeigler
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> While working on an application, I noticed that my objects were being
> serialized "weird" into a form by the loop component. I realized that I
> hadn't provided the primary key encoder, and once I did things worked as
> expected. That got me to thinking that it would be nice if the Loop
> component, and other components that rely on PrimaryKeyEncoders, could check
> to see if there is an encoder available for the value-type, if none is
> explicitly bound by the user. That way, module-authors could provide
> PrimaryKeyEncoders that makes things work "like magic".
> For example, tapestry-hibernate could contribute PrimaryKeyEncoders for each
> entity type so that the objects are automatically, and properly, encoded into
> forms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
