Tapestry
  1. Tapestry
  2. TAPESTRY-1900

Allow multiple markers annotations per service

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.6
    • Fix Version/s: 5.0.7
    • Component/s: None
    • Labels:
      None

      Description

      Currently, each service is associated with a single marker annotation. I can forsee cases where multiple marker annotations would be helpful. Thus, the @Marker annotation should support a list of annotation classes, and the marker annotations for a service should be additive: the module's marker annotations plus the annotations specified by ServiceBinderOptions.withMarker(), plus the annotations from the @Marker annotation on the implementation class or service build method.

        Activity

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development