You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Martin Maier-Moessner (JIRA)" <de...@myfaces.apache.org> on 2014/07/08 15:09:05 UTC

[jira] [Updated] (ORCHESTRA-67) Allow Orchestra annotations to be used in meta annotations

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

Martin Maier-Moessner updated ORCHESTRA-67:
-------------------------------------------

    Status: Patch Available  (was: Open)

> Allow Orchestra annotations to be used in meta annotations
> ----------------------------------------------------------
>
>                 Key: ORCHESTRA-67
>                 URL: https://issues.apache.org/jira/browse/ORCHESTRA-67
>             Project: MyFaces Orchestra
>          Issue Type: Improvement
>          Components: Conversation
>    Affects Versions: 1.5
>         Environment: Java 7, Spring 4.0
>            Reporter: Martin Maier-Moessner
>
> Currently, orchestra does not allow annotations like @ConversationName or @ConversationRequire to be used on Spring meta annotations (http://docs.spring.io/spring/docs/4.0.x/spring-framework-reference/htmlsingle/#beans-meta-annotations). It would be very comfortable if one could create a meta annotation for a group of classes and having to define the conversation name only once.
> To implement this, Orchestra simply has to call AnnotationUtils.findAnnotation() instead of clazz.getAnnotation() in AnnotationInfoManager.



--
This message was sent by Atlassian JIRA
(v6.2#6252)