You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2009/02/10 03:12:59 UTC

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

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


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.