[
https://issues.apache.org/jira/browse/WICKET-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arni Kekoni updated WICKET-3947:
--------------------------------
Attachment: Wicket-3947-1.4.x.patch
Patch for 1.4.x
JUnit tests attached to this issue are all green with this patch. Fix is not
the most elegant one, but should give some insight on to the actual problem.
As stated before there is no easy (and good) solution for this issue.
InlineEnclosure is an auto component and can therefore reside under other auto
components in markup tree. These auto components are removed during detach and
while InlineEnclosure is not (as a special case) it is left without a parent.
This patch simply reparents the inline enclosure to the first non transparent
resolver it can find in the component tree. Algorithm is exactly the same as
can be found in Enclosure class.
Comments?
> Inline Enclosure does not work properly when using wicket:extend and
> wicket:child
> ---------------------------------------------------------------------------------
>
> Key: WICKET-3947
> URL: https://issues.apache.org/jira/browse/WICKET-3947
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC5.1
> Reporter: Krys Malak
> Labels: enclosure, extend
> Attachments: Wicket-3947-1.4.x.patch, karsinta.zip, variation.zip
>
>
> When using Inline Enclosures describes in
> https://issues.apache.org/jira/browse/WICKET-3422 the functionality is broken
> in a page that uses wicket:extend and wicket:child.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
