You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/09/09 00:51:44 UTC

[jira] Closed: (TAPESTRY-1875) Add package level to regex in @Match annotation for service decorators

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

Howard M. Lewis Ship closed TAPESTRY-1875.
------------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

This is counter to the direction of T5 IoC, which is to get further away from names and base things more on annotations.  For your rule, you could attach a marker annotation on individual services, or on an entire module, to trigger the decoration you desire.

> Add package level to regex in @Match annotation for service decorators
> ----------------------------------------------------------------------
>
>                 Key: TAPESTRY-1875
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1875
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-ioc
>    Affects Versions: 5.0.7
>            Reporter: Paul Cooley
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> Instead of simply matching on the name, there are cases where a specific decorator need only match certain package level services.  For instance, to create a mandatory decoration for all of my company's services where the package name begins with "com.coname", the @Match("com.coname.*") should then be added for every service interface that bears that package name.

-- 
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