[jira] [Resolved] (WICKET-5458) Problems with nested InlineEnclosures and InlineEnclosures on pages with inherited markup

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov resolved WICKET-5458.
-------------------------------------

    Resolution: Won't Fix

Wicket 1.4.x is not maintained anymore.
It receives only security related fixes and this problem is not considered as such.
Thanks!

> Problems with nested InlineEnclosures and InlineEnclosures on pages with inherited markup
> -----------------------------------------------------------------------------------------
>
>                 Key: WICKET-5458
>                 URL: https://issues.apache.org/jira/browse/WICKET-5458
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.22
>            Reporter: Anssi Luukkonen
>              Labels: enclosure
>         Attachments: Patch for WICKET-5458.patch
>
>
> This issue is a continuation of cases WICKET-3947 and WICKET-4700. InlineEnclosures have problems especially in 1.4.x branch. InlineEnclosures do not function on pages that use wicket:extend and wicket:child. Also nested InlineEnclosures and components inside InlineEnclosures have problems with Ajax.
> There is also another problem with InlineEnclosures in 1.4.x branch. If InlineEnclosures are used on a page that is not cached (i.e. page that implements IMarkupCacheKeyProvider with method getCacheKey returning null), InlineEnclosures will get new id in markup every time page is reloaded. As a result markup is not found for InlineEnclosures previously added to the page, as they have ids that were generated first time the page was loaded.



--
This message was sent by Atlassian JIRA
(v6.2#6252)