Tapestry 5
  1. Tapestry 5
  2. TAP5-1535

When there's a type mismatch between a container component at the field with @InjectComponent, the type of the containing component should be part of the exception message

    Details

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

      Description

      Currently, the name of the field with @InjectComponent is identified, as is the type of that field, but it would make it easier to debug what's gone wrong if the type of the container component was also in the message, as that's not always obvious from the container's component id.

        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