Re: WOHyperlink doesn't always call its action
Re: WOHyperlink doesn't always call its action
- Subject: Re: WOHyperlink doesn't always call its action
- From: Chuck Hill <email@hidden>
- Date: Mon, 20 Dec 2010 10:50:33 -0800
This is "as designed". See WOApplication:
setPageRefreshOnBacktrackEnabled
public void setPageRefreshOnBacktrackEnabled(boolean aFlag)
When aFlag is true, disables caching of pages by the client by setting the page's expiration-time header to the current date and time. By default, this attribute is set to true. Disabling of client caching affects what happens during backtracking. With client caching disabled, the browser resends the URL to the server for the page requested by backtracking. The application will then return a new page to the browser (corresponding to a new WOComponent instance). This behavior is desirable when you do not want the user to backtrack to a page that might be obsolete because of changes that have occurred in the session.
When this flag is turned on 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.
You can turn this off if you want. A WOSubmitButton might work if the Form is set to POST, not the default of GET.
Or use Ajax instead of frames. :-)
Chuck
On Dec 20, 2010, at 6:09 AM, Perry, Steven wrote:
> I have a situation where a WOHyperlink sometimes does not call the designated “action”.
>
> Hyperlink looks like this:
>
> Hyperlink1: WOHyperlink {
> action = selectRecord;
> target = “Content”;
> }
>
> The page has frames and the hyperlink is used to select a record from the list frame, and display its data in the detail frame.
> · When I click the hyperlink for record #1, selectRecord is called and data displays just fine.
> · When I click the hyperlink for a different record (#2), selectRecord is called, and the new record is displayed.
> · When I reclick the hyperlink for record #1, selectRecord is not called, and record #2 remains.
>
> We’ve tried changing the WOHyperlink to a WOSubmitButton (with a WOForm around it)... same result.
>
> Any thoughts?
>
> _______________________________________________
> 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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects
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