How should I better handle loading of Wicket Models when using Wicket forms?

To answer my own question, the problem I was experiencing was that the model that was bound to the form appeared to persist every time I returned to the page. This led me to believe the problem was how I was managing models, but the problems was actually related to how I was linking to pages.

While the link method (previous answer) could pose a problem and often does depending on how you implement a link, the actual problem in this case was with the "EntityFactory" that was being used to load the instance of the domain object. In this case, it was providing cached data instead of instantiating a new instance.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.