You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/03/22 20:14:27 UTC

[jira] Updated: (TAP5-1067) Created component constructor may use too many parameters

     [ https://issues.apache.org/jira/browse/TAP5-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1067:
---------------------------------------

    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.

  was:The constructor crated 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.


> Created component constructor may use too many parameters
> ---------------------------------------------------------
>
>                 Key: TAP5-1067
>                 URL: https://issues.apache.org/jira/browse/TAP5-1067
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.