Tapestry
  1. Tapestry
  2. TAPESTRY-2567

Tapestry doesn't identify conflicting annotations on component fields

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.14
    • Fix Version/s: 5.0.15
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Currently, as the worker for an annotation is activated for a particular field, the field is "claimed" by the annotation.

      When searching for fields with a given annotation, previously claimed fields are ignored.

      Thus if you use conflicting annotations, such as @Persist and @Parameter, you get no error and it's a guess as to which takes effect.

      Instead, we should see a failure when the second annotation work tries to re-claim the field. The exception should identify how the field was claimed, for example, by identifying the annotation (or at least, annotation type) for which the field was claimed.

        Activity

        There are no comments yet on this issue.

          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