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)" <ji...@apache.org> on 2008/10/16 19:23:45 UTC
[jira] Updated: (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 updated TAP5-60:
-------------------------------------
Issue Type: Improvement (was: Bug)
> 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
> Affects Versions: 5.0.15
> Reporter: Howard M. Lewis Ship
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org