Tapestry 5
  1. Tapestry 5
  2. TAP5-783

tapestry should mark via annotation which annotations are component-specific vs. more general

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Many annotations used by tapestry (@Parameter, etc.) are used only in the context of component classes. Others (@InjectService) can be used in multiple contexts. It would be nice if tapestry used a documented annotation to note this distinction.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Robert Zeigler
            Reporter:
            Robert Zeigler
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development