You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/26 00:42:59 UTC

[jira] Closed: (TAP5-60) Provide an alternate approach to decorating services based on aspects

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

Howard M. Lewis Ship closed TAP5-60.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.0

> Provide an alternate approach to decorating services based on aspects
> ---------------------------------------------------------------------
>
>                 Key: TAP5-60
>                 URL: https://issues.apache.org/jira/browse/TAP5-60
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.0
>
>
> It would be nice if decorators could be passed an AspectInterceptorBuilder and could choose to advise methods.  Such a decorator method could return void, and would not need to have the delegate passed in.
> Difficulty: what is the order when a single service has advised methods and interceptors (via traditional 5.0-style decorators)?  All the advised method changes would be grouped together and the outcome may not be as desired.  It may be required that any single service have 5.0 style decorators or 5.1 style aspects, but not both.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.