[jira] [Closed] (TAP5-509) Create an AnnotationProvider pipeline

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade closed TAP5-509.
-------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

> Create an AnnotationProvider pipeline
> -------------------------------------
>
>                 Key: TAP5-509
>                 URL: https://issues.apache.org/jira/browse/TAP5-509
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.0.18
>            Reporter: Thiago H. de Paula Figueiredo
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> An AnnotationProvider pipeline would provide two very nice features:
> * The possibility of converting one annotation into another. This could easily allow for Tapestry-IoC recognize Spring or EJB or Guice dependency-injection annotations, for example.
> * The possibility to easily add annotations to classes, fields and methods that do not have them. Example: use of JPA and Hibernate Validator annotations to provide BeanEditor/BeanEditForm validation without using @Validate on the entity classes. Maybe we need an specialized validation pipeline, as JPA annotations (@Column(nullable= false), for example) would add one validation rule, but Hibernate Validator (@Email) would provide another validation rule, not overwriting the first one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)