[
https://issues.apache.org/jira/browse/TAPESTRY-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620977#action_12620977
]
Kevin Menard commented on TAPESTRY-2491:
----------------------------------------
I had voiced similar concerns in the past. It can just be downright confusing.
Just earlier today I was trying to help someone (that's been using the
framework for a while) on IRC understand the differences, which are quite
subtle.
> Components which use PrimaryKeyEncoder should be changed to use ValueEncoder,
> and PrimaryKeyEncoder should be eliminated.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2491
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2491
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.14
> Environment: any
> Reporter: Robert Zeigler
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
