On 14.04.2012 16:38, Emmanouil Batsis (Manos) wrote:
On 04/14/2012 03:03 PM, Christoph Leiter wrote:
Here's a good article about EntityModel, which does what you want:
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
Sorry for jumping in but wanted to make sure I get this
Just keep in mind that you can't use an EntityModel if the entity has already
been persisted and if you want to change it with multiple ajax
requests/multistep forms. It will lose any changes on every request. Simply
serialize the entity again for that use case.
Stealing the thread back
Another newbie question; it is now the case that each model is serialized
between requests and (I presume) stored in the session. I would really prefer
if a identifier (primary key + lazy locking versionnr) could be remembered and
that each time when Wicket needs the model, it is loaded from
Look at LoadableDetachableModels .
Josh.
On Sat, Apr 14, 2012 at 2:38 PM, Tom Eugelink t...@tbee.org wrote:
Another newbie question; it is now the case that each model is serialized
between requests and (I presume) stored in the session. I would really
prefer if a identifier (primary key +
Here's a good article about EntityModel, which does what you want:
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
Christoph
Tom Eugelink (2012-04-14 13:38):
Another newbie question; it is now the case that each model is
serialized between requests and (I presume) stored in
On 04/14/2012 03:03 PM, Christoph Leiter wrote:
Here's a good article about EntityModel, which does what you want:
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
Sorry for jumping in but wanted to make sure I get this right. In the
example given above, does it make sense to
Thanks! This looks very promising!
On 2012-04-14 14:03, Christoph Leiter wrote:
Here's a good article about EntityModel, which does what you want:
http://wicketinaction.com/2008/09/building-a-smart-entitymodel/
Christoph
W dniu 2012-04-14 13:38, Tom Eugelink pisze:
Another newbie question; it is now the case that each model is serialized
between requests and (I presume) stored in the session. I would really prefer
if a identifier (primary key + lazy locking versionnr) could be remembered and
that each time
