|
Hi, I had considered doing something like that but i find that if the message is displayed on page with other information, such as displaying the "successfully updated" message on the actual form, its not as easy to notice. Feedback from the majority of users that have used systems like this dont mind it and like the consistent confirmations. Also (i'm not sure how applicable to JSF this i) the redirection stops the browser from ending on a page that can have post data re-submitted if refreshed. Ie. it prevents people from re-doing some action without noticing. Anyway thanks for your input and I will seriously consider an approach like you mentioned as it does seem to be much more suited to the framework. Thanks, -Robert. Andrew robinson wrote: Not to question your design, but why have an extra page and make the user wait for a post back. Instead of a redirection, just add "Your order was completed successfully" as a FacesMessage with no associated component, then on every page on your site, have a messages tag to show all non-component messages. That way, all pages that are loaded after your change will show the "all is well" message. The user can then immediately get back to work, and not have to wait for another post back and you also won't have to worry about browsers supporting the meta-refresh tag.Just a thought, Andrew On 11/2/05, Robert Parsons <[EMAIL PROTECTED]> wrote: |
- Re: Generic redirection screen Robert Parsons
- Re: Generic redirection screen Robert Parsons
- Re: Generic redirection screen Robert Parsons

