Tapestry 5
  1. Tapestry 5
  2. TAP5-60

Provide an alternate approach to decorating services based on aspects

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-ioc
    • Labels:
      None

      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

          Activity

          Hide
          Howard M. Lewis Ship added a comment -

          This only makes sense if the AIB can advise the same method multiple ways.

          Show
          Howard M. Lewis Ship added a comment - This only makes sense if the AIB can advise the same method multiple ways.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development