[jira] [Resolved] (WICKET-5479) Header rendering of components inside of InlineEnclosure

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

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

Martin Grigorov resolved WICKET-5479.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0.0
         Assignee: Martin Grigorov

Fixed by using the new queueing mechanism (WICKET-3335) - https://www.42lines.net/2014/02/28/component-queueing-in-wicket-7/

This is the new code:

link1.setOutputMarkupPlaceholderTag(true).setVisible(false);
queue(activate, link1, link2);

> Header rendering of components inside of InlineEnclosure
> --------------------------------------------------------
>
>                 Key: WICKET-5479
>                 URL: https://issues.apache.org/jira/browse/WICKET-5479
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.13.0
>            Reporter: Fridolin Jackstadt
>            Assignee: Martin Grigorov
>              Labels: enclosure
>             Fix For: 7.0.0
>
>         Attachments: ajax-enclosure.zip
>
>
> AjaxLink inside of an InlineEnclosure doesnt work, if container is made visible via ajax.
> It is possible to use a WebMarkupContainer instead as workaround.
> The Question is: should the InlineEnclosure work, which looks straight forward to me, or is this problem hard to fix and I should keep using the workaround?



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