Wicket components not being created when visible = false

Came across an interesting one today... if you have a component in Wicket with visible=false when the page is rendered the first time, the markup for that component is not sent to the browser at all. The end result is that you cannot use Ajax to make the component visible at a later stage. Turns out there is an easy way around this though, just call setOutputMarkupPlaceHolderTag(true) on the component, and a placeholder tag is sent ot the browser, which can later be replaced with Ajax.