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

Persistence strategy should alternately be specified via an annotation on the persisted field

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Abandoned
    • 5.0.15
    • None
    • None
    • None

    Description

      Currently you must use a name (or constant) to define the persistence strategy. Using a name will always be less refactoring safe than an annotation.

      With just @Persist (the empty string value) a search based on meta data is started.

      It would be nice if there was a way to inject some logic that could check for an auxiliary annotation or other bit of logic to decide the persistence strategy.

      Ideally, when using tapestry-hibernate and a field is an entity type defined in Hibernate, the "entity" persistence strategy should be the default, before checking meta data.

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: