Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1067

Created component constructor may use too many parameters

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.2.0
    • 5.2.0
    • tapestry-core
    • 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment