tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H de Paula Figueiredo" <thiag...@gmail.com>
Subject Re: [jira] [Created] (TAP5-2491) Default marker annotation
Date Fri, 28 Aug 2015 15:07:04 GMT
Hi!

Another day I was thinking exactly the same Nathan posted below. I suggest  
using adding this rule: when more than one service matches the requested  
service, but only one of them has the @Primary annotation from  
tapestry5-annotations, return it.

What do you guys think? It would be helpful specially for objects  
contributed to a service configuration and you want them to be services by  
themselves.

On Tue, 25 Aug 2015 10:15:45 -0300, Nathan Quirynen (JIRA)  
<jira@apache.org> wrote:

> Nathan Quirynen created TAP5-2491:
> -------------------------------------
>
>              Summary: Default marker annotation
>                  Key: TAP5-2491
>                  URL: https://issues.apache.org/jira/browse/TAP5-2491
>              Project: Tapestry 5
>           Issue Type: Improvement
>           Components: tapestry-core
>     Affects Versions: 5.3.7
>             Reporter: Nathan Quirynen
>             Priority: Minor
>
>
> It would be nice when making use of Marker annotations for tagging a  
> service, that a default marker value could be defined. So when no marker  
> annotation is added to the injection of the service this defined default  
> will be used.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)


-- 
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message