Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-60

Provide an alternate approach to decorating services based on aspects

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

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

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              hlship Howard Lewis Ship
              Reporter:
              hlship Howard Lewis Ship

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment