Tapestry 5
  1. Tapestry 5
  2. TAP5-1067

Created component constructor may use too many parameters

    Details

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

      Description

      The constructor created for components can fail for components with large numbers of fields, since typically at least one constructor parameter is added per field (due to injections, etc.). Passing in the dependent objects (ComponentValueProviders and FieldValueConduits) as an Object[] array would bypass this problem.

      In addition, the greater use of component method advice introduces yet more values passed into the component constructor.

        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