StaleLink Excpetion in Tapestry

[Amit <am...@fxall.com>]

Hi,

We have one application ruuning based on the Tapestry framework. We are getting 
Stalelink exception while trying out the following stuff:

We have two browser instances open. We have used dropdown and checkboxes.

In one instance a checkbox appears which displays the state as 'Pending'.

In another instance we have changed the selection from 'Pending' to 'Approved' 
and submitted the form. The state is changed to 'Approved' in the database.

Now we go back to the first instance , checked the checkbox against 'Pending' 
anc clicked 'Submit'.

Now what is happening is that we are trying to save 'Pending' state in one 
instance that had already been changed to 'Approved' in the other instance.
So the page having 'Pending' state throws a stale link excpetion.

We have used @foreach component at numerous places. So replacing @foreach by 
@ListEdit doesn't seem to be feasible solution for us at all as we have to do a 
lot of rework.

Is there any other simple solution that doesn't require much rework.

Please let us know your suggestions.

Thanks,
Amit




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: StaleLink Excpetion in Tapestry

[Bryan Lewis <br...@maine.rr.com>]

Second the motion for ListEdit.  It's a drop-in replacement for Foreach,
using the same parameters. A global search and replace might be the extent
of the rework.


----- Original Message ----- 
From: "Kent Tong" <ke...@cpttm.org.mo>
To: <ta...@jakarta.apache.org>
Sent: Wednesday, March 09, 2005 8:51 PM
Subject: Re: StaleLink Excpetion in Tapestry


> Amit <amit.gupta <at> fxall.com> writes:
>
> > We have used  <at> foreach component at numerous places. So replacing
<at>
> > foreach by
> >  <at> ListEdit doesn't seem to be feasible solution for us at all as we
> > have to do a lot of rework.
> >
> > Is there any other simple solution that doesn't require much rework.
>
> ListEdit is the way to go, but if you really want to stick
> with Foreach, you may try making your list persistent.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: StaleLink Excpetion in Tapestry

[Kent Tong <ke...@cpttm.org.mo>]

Amit <amit.gupta <at> fxall.com> writes:

> We have used  <at> foreach component at numerous places. So replacing  <at> 
> foreach by 
>  <at> ListEdit doesn't seem to be feasible solution for us at all as we 
> have to do a lot of rework.
> 
> Is there any other simple solution that doesn't require much rework.

ListEdit is the way to go, but if you really want to stick
with Foreach, you may try making your list persistent.


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

RE: StaleLink Excpetion in Tapestry

[Wayne Andersen <wa...@clima-tech.com>]

Amit, I am kind of a new user here but the situation yu describe is
exactly the way things should work. The system is notifiying the user via
the stale link exception of what you already know. The object they are
dealing with has changed since they retreived it.

Changing the component won't have any effect on this. What is it you are
looking for, do you want to (1) allow the process even though the link is
stale, (2) Have a better/friendlier notification?

Wayne L Andersen
System Administrator
Clima-Tech Corporation
208-947-1849



-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Amit
Sent: Wednesday, March 09, 2005 8:29 AM
To: tapestry-user@jakarta.apache.org
Subject: StaleLink Excpetion in Tapestry


Hi,

We have one application ruuning based on the Tapestry framework. We are
getting
Stalelink exception while trying out the following stuff:

We have two browser instances open. We have used dropdown and checkboxes.

In one instance a checkbox appears which displays the state as 'Pending'.

In another instance we have changed the selection from 'Pending' to
'Approved'
and submitted the form. The state is changed to 'Approved' in the
database.

Now we go back to the first instance , checked the checkbox against
'Pending'
anc clicked 'Submit'.

Now what is happening is that we are trying to save 'Pending' state in one

instance that had already been changed to 'Approved' in the other
instance. So the page having 'Pending' state throws a stale link
excpetion.

We have used @foreach component at numerous places. So replacing @foreach
by
@ListEdit doesn't seem to be feasible solution for us at all as we have to
do a
lot of rework.

Is there any other simple solution that doesn't require much rework.

Please let us know your suggestions.

Thanks,
Amit




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org