Dunno if that is your problem but one of the most likely causes is
having the underlying array of a WORepetition change between the time
it rendered and the time the link was clicked (object inserted/
deleted, sort order changed, batch size changed etc). You have these
options:
- use Direct actions inside of WOReps. Works, but is a lot of code to
write.
- warn user when he backtracks. Works, but is very unfriendly
- rewrite WORepetition to use more info than just the index number
when the link was generated.
The last part is done in ERXWORepetition in Project Wonder. Instead
of the index number we use the System.identityHashCode(item) and if
that doesn't match either throw an exception or re-render the page.
Cheers, Anjo
Am 17.04.2006 um 20:34 schrieb Jonathan Miller:
Hi,
I'm following Apple's Guidelines on setting up server side page
caching (i.e. setPageRefreshOn... && setPageCacheSize(int)) but it
doesn't seem to be working...
e.g. when someone hits the back button and then uses a WOHyperlink
w/n the page it performs the wrong action.
Does anyone have some wisdom they can share in regards to this?
Thank you
Johnny
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/krank%
40logicunited.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
