You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/07/11 12:03:49 UTC

[jira] [Resolved] (WICKET-5268) ComponentRenderer.renderComponent fails to render two components with different component IDs

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

Martin Grigorov resolved WICKET-5268.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 6.10.0
                   7.0.0
         Assignee: Martin Grigorov
    
> ComponentRenderer.renderComponent fails to render two components with different component IDs
> ---------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5268
>                 URL: https://issues.apache.org/jira/browse/WICKET-5268
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.9.0
>            Reporter: Edvard Fonsell
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 7.0.0, 6.10.0
>
>
> After WICKET-5232 was fixed, #renderComponent now accepts component with any component ID. However since the markup of the RenderPage is cached, after calling #renderComponent for one component it will fail for components having different component ID.
> This could be fixed as I suggested in WICKET-5232: RenderPage could implement IMarkupCacheKeyProvider interface and return null in #getCacheKey.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira