the problem is most of the time with model objects
is that when you have set it. Then that is also a database operation
So going back into history with the browser and revering the model object
doesn't make much sense then
because then you also have to revert the database ooperation
So model object versioning only makes sense when the object is in mem (like
your counter)
onClick()
{
Integer counter = getModelObject()
setModelObject(counter+1)
}
johan
On Sat, Mar 15, 2008 at 4:27 PM, James Carman <[EMAIL PROTECTED]>
wrote:
> On 3/15/08, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > in what context?
> >
> > you with your counter shouldn't touch the model things anyway
> > just do wat Matej told you and use addStateChange()
> > thats is what you should do
>
> Well, I'm just trying to come up with a real-world example. I guess
> in the real world, I'd be doing something in the link's onClick()
> method that modifies some model object. So, I'd be modifying an
> Address for instance (let's say I have a link that says "copy my
> billing address" or something) that's being displayed in some form.
> In that case, I would call modelChanging()?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
