Models have been my achilles heel when it comes to Wicket. Not so much their
explicit use, but understanding whe they data they wrap around is serialized
or kept in session and when it's not. I was running some tests today to
experiment with just this subject. The domain object I was using in my te
Matthew,
A quick absolute way to make sure those values are serialized is to use the
Java 'transient' keyword. But Wicket will be assuming that when a user hits
the Back button, that it can re-constitute the page from the serialized info
it has on disk, if it cannot, then yes you'll need a Loadabl
I found Igors post on smart entity models very helpful on that matter:
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
basically, it attaches/detaches only if an Id is set (hence, it can be fetched
from the backend)
Bert
--
I had read that blog entry several times before but the significance of that
last part hadn't stuck with me. I adapted my entity model (using Neo4J not
Hibernate) and it looks like a good solution. Thanks for the pointer!
--
View this message in context:
http://old.nabble.com/Serialization-and
