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

The ValueEncoder for JPA entity types should encode transient instances as null rather than throw an exception

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.3.3, 5.3.4
    • 5.3, 5.4
    • tapestry-jpa
    • None

    Description

      The current behavior gets in the way in many cases, such as creating a single page that will either edit an existing entity or editing a newly created entity before its first save, where the instance (transient or persistent) is stored as page activation context.

      Same bug for Tapestry-Hibernate was resolved from Howard
      https://issues.apache.org/jira/browse/TAP5-1641

      Attachments

        Activity

          People

            tawus Taha Hafeez Siddiqi
            zenios Dimitris Zenios
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: