I think you may be able to separate those things into transactions
using spring annotation based transactions?
So then you can handle your transactions being created / flushed by a
method scope - so the data will be flushed to DB when the method
invokation is finished.
You can read more at:
http:
dont think a conversation scope will be of much help to you. wicket
does support it via jboss' cdi implementation, but i think you are
better off stashing all the changes into some dto and applying them
when the save button is pressed.
-igor
On Mon, May 3, 2010 at 12:13 PM, Ray Weidner
wrote:
>
I have a question about how to approach a certain kind of problem. Let me
first explain what I'm doing, and then what the problem is with that.
For the web app I'm creating, a user can, using a web form, edit data which
is backed by a model that fetches the persistent object being modified.
Whe
