Enclosure was never able to work in Ajax. That's why InlineEnclosure has been introduced.
On Sat, Apr 7, 2012 at 6:04 PM, Bertrand Guay-Paquet <[email protected]> wrote: > Hi, > > After creating the EnclosureContainer, add the following call : > container.setRenderBodyOnly(false); > > In the EnclosureContainer's constructor, this is actually set to true which > means that the HTML tag is not part of the rendered markup if the Enclosure > is not visible on first render. When made visible afterwards via Ajax, > Wicket js cannot find the tag to replace with the enclosure's content. > > In my opinion, this is a bug and a JIRA issue should be created. > > > On 07/04/2012 1:46 AM, Douglas Ferguson wrote: >> >> Is this expected behavior? Is there a workaround? >> >> On Apr 5, 2012, at 6:58 PM, Douglas Ferguson wrote: >> >>> I just found a different between 1.4 and 1.5 with regards to wicket >>> enclosure. >>> >>> If you have a component in a wicket enclosure (say a feedback panel) and >>> you set it visible false. >>> Then subsequently try to set it visible true, wicket 1.5 will not be able >>> to make it reappear. >>> >>> 1.4 had no problem with this. >>> >>> I get this in the debugger console: >>> >>> ERROR: Wicket.Ajax.Call.processComponent: Component with id [[id3]] was >>> not found while trying to perform markup update. Make sure you called >>> component.setOutputMarkupId(true) on the component whose markup you are >>> trying to update. >>> >>> Douglas >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
