Yes, you still deal with detached entities
(LazyInitializationException, StaleStateException, last writer wins, etc).
And worse in my opinion, it makes things different when responding from the
latest page vs. a page recovered with the back button, or if another
window/tab has made an intervening r
On Fri, May 4, 2012 at 6:15 PM, Dan Retzlaff wrote:
> I'll mention one hack for which another Wicket user should rightly
> reprimand me. As I mentioned recently, Wicket keeps the most recently
> accessed page is a deserialized state to optimize serving the next request.
> All components are still
true...
> Date: Fri, 4 May 2012 15:15:08 -0700
> Subject: Re: Store models short-term
> From: dretzl...@gmail.com
> To: users@wicket.apache.org
>
> Hi, Jason. Welcome to Wicket!
>
> If you want to tie an entity to a page, best save the entity within the
> page itself. Y
Hi, Jason. Welcome to Wicket!
If you want to tie an entity to a page, best save the entity within the
page itself. You can do this by using a simple o.a.w.model.Model. If you
don't want to detach between requests, then LDM is not a good fit.
There are use cases where serializing entities at the a
I'm new to Java and Wicket. My only previous experince with web applications
has been with Asp.net forms (not MVC). Please be patient; coming from the
postback event paradigm, I'm struggling to grasp the concepts in Wicket. In my
simple scenario, assume there is no AJAX. I need to build the mod
