So the Sorting DataView Example at wicket-library.com is overkill? It uses an
LDM, and that's what I based
my own implementations on before.
--
View this message in context:
http://n4.nabble.com/What-is-the-best-way-to-use-LoadableDetachableModel-with-a-WebPage-and-DataView-tp2016027p20
why all the complexity of ldm inside idataprovider, why not just:
class mydataprovider implements idataprovider {
private long applicantid;
private transient applicant applicant;
private applicant getapplicant() { if (applicant==null) {
applicant=dao.get(applicantid); }}
private iterator(.
Hi All,
I need help with a Wicket architecture design issue that I am having.
In previous Wicket applications, I have used the LoadableDetachableModel in 2
separate ways:
1) In the constructor of a WebPage, an LDM is instantiated and then used as the
model
for a component such as a ListView. T
