Hi all,
Our Wicket 1.4 project (currently 1.4.3) uses tabs on some pages to display
linked information. For example, an Account may have a User. On the Account
page, there would be a User tab in this case. The User is a PropertyModel
on a LoadableDetachableModel for the Account (which grabs from
Wicket needs to detach the replaced panel because it is no longer
attached to the component hierarchy. If we didn't detach at that time,
hell [c/w]ould break loose.
We assume with loadable detachable models that people use proper
caching such that the database won't be hit hard. E.G. if you use
I do understand and appreciate the need to detatch the models. It's just
that if the detached happened a few lines earlier, before the new tab is
instantiated, it would be a lot less error prone with respect to
accidentally causing more db load.
Current mechanism:
1. Instantiate new tab (causes
