A workaround to the lazy-init-in-view problem.
We hand out DisconnectableConnections to the JPA-implementation, now,
if a lazy-init happens during the view rendering we are able to disconnect it again
at the end of the request (using a servlet filter).
check if we already added components to the layout component.
if this is the case then:
keep them cached and avoid readd
in development mode: remove the componentsin production mode: keep them cached
TODO: need to figure out whats the best way to recreate the components