[jira] Updated: (TAP5-55) Persistence strategy should alternately be specified via an annotation on the persisted field

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-55:
-------------------------------------

    Issue Type: Improvement  (was: Bug)

> Persistence strategy should alternately be specified via an annotation on the persisted field
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAP5-55
>                 URL: https://issues.apache.org/jira/browse/TAP5-55
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>
> 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.

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org