the markup gets loaded. Two possible solutions: a) stay with adding auto components at render time
b) make the *Targets responsible to
re-create the autocomponents and only than render the page.
i dont like this at all. it adds a requirement for targets that cannot be clearly expressed through the interface. Solution (a) questions a little bit our vision thats ok, maybe we can fix it all the way in v3 and (b) will end up
with where does the render process start and where does it end.
yes, this is bad Solution (a) has another drawback: if we really want to achieve a 1:1
relationship between markup and component hierarchy than there will be scenarios where components are inside <wicket:head> and when we remove the wicketHead container at the end of the render cycle, that it removes the inner component(s) as well.
can we somehow get around removing the entire head component? -igor
Juergen
