Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-165

Components which use PrimaryKeyEncoder should be changed to use ValueEncoder, and PrimaryKeyEncoder should be deprecated

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.0.16
    • Fix Version/s: 5.1.0.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      any

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              ongakugainochi Robert Zeigler
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: