SOLVED: request-response loop question
SOLVED: request-response loop question
- Subject: SOLVED: request-response loop question
- From: Tom Woteki <email@hidden>
- Date: Mon, 15 Nov 2004 15:58:02 -0500
Thanks. I solved it with the tip below:
On Nov 15, 2004, at 2:52 PM, Chuck Hill wrote:
I have logged the request response loop. The second time I click on a
link, the loop proceeds only to awaken the component which contains
the WOHyperlink, but it never invokes action that is bound to the
link (invokeAction is not called), which is just another way of
saying everything above.
In order to prevent the worst ravages of backtracking, WO caches URLs
and responses. If a previously processed URL is requested, the page
is awoken and appendToResponse run. That sounds to me like what is
happening in your case. Here are some ideas on a solution:
- disable this backtracking protection. At the very least, this is a
quick way to prove or disprove my theory. See the WOApplication
method setPageRefreshOnBacktrackEnabled
Perfect. The documentation for this method explains my situation to a
T: "When this flag is turned on [default] and a request corresponding
to a client backtrack occurs, the retrieved page will only be asked to
regenerate its response. The first two phases of a normal
request-response loop (value extraction from the request and action
invocation) do not occur. "
In inserted complementary false-true calls to
setPageRefreshOnBacktrackEnabled in awake and sleep and I now have the
desired behavior.
- it sounds like your action method is not returning a new component
instance (e.g. doing a pageWithName), but instead returning the same
instance configured to display a different object. While this
conserves memory, it can conflict with the multiple state caching of
WO's backtrack refreshing. If you always return a new instance this
should go away.
Actually I was already using pageWithName in my action. But as
explained above, the r-r loop never got into the invokeAction phase.
Thanks again.
Tom
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden