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/04/28 13:38:16 UTC

[jira] [Reopened] (WICKET-5085) InlineEnclosure are piling up on each render

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

Martin Grigorov reopened WICKET-5085:
-------------------------------------

      Assignee: Martin Grigorov  (was: Sven Meier)

There is still problem with unique id of InlineEnclosures.
The introduced counter is field member of InlineEnclosureHandler but IMarkupFilter instances are not shared between markup files. I.e. MyPanelA will use instance of InlineEnclosureHandler and MyPanelB will use another instance of InlineEnclosureHandler. So their produced markup will have unique 'counter' by its own, but the counters will collide in the final page markup.
                
> InlineEnclosure are piling up on each render
> --------------------------------------------
>
>                 Key: WICKET-5085
>                 URL: https://issues.apache.org/jira/browse/WICKET-5085
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.6.0, 1.5.10
>            Reporter: Sven Meier
>            Assignee: Martin Grigorov
>             Fix For: 6.7.0, 1.5.11
>
>
> InlineEnclosureHandler#resolve() uses an auto-incremented id for its resolved InlineEnclosure, 
> On the next render, a new instance will be resolved, since the id of the already resolved InlineEnclosure does not match the id in the markup.
> But InlineEnclosures are not removed after render as other auto-components, thus all instances pile up in the owning container of the markup.

--
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