[TAP5-60] Provide an alternate approach to decorating services based on aspects

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.1.0.0
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 20/Aug/08 15:23
• Updated: 02/May/13 02:29
• Resolved: 25/Jan/09 23:42

Description

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.

Issue Links

• depends upon: TAPESTRY-2584 AspectInterceptorBuilder should allow for multiple advice per method
• is related to: TAP5-465 Add a LazyAdvisor service that can allow method invocations on services to be lazily evaluated