On 11/15/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I'm trying to use the new dialog stuff in a production app. Previously I had only been using dialogs in popup windows (with no browser back buttons to worry about.) Now I think I'm running into the same problems as Rahul and others have reported. I will describe my usecase where I think the results are unexpected. I'm working on a website for a marina. Most of the site navigation links bring up other pages but when they click on "boats", a shale dialog is started that helps them to browse the list of available boats. The dialog is completely transparent to the user. The same site menu navigation options appear on the page and the user has no idea they are in a dialog. If in the middle of browsing through the listing the user wants to start over they will likely click the "boats" link again. This time it appears to do nothing. In reality its starting the dialog which is picking up where it "left off." The end result is the user is "stuck." Is this really desirable behavior? Maybe we should at least have the option to restart the dialog? Also, if the user bookmarks any of the pages in the dialog, they are pretty much screwed. I realize there is a larger bookmarking in JSF issue here but I'm looking for some ideas.
IIRC, you filed some RFE requests against dialog for a similar use case, and we listened :-). You can fake a restart by programmatically stopping the current dialog, and then programmatically starting a new one. Does that do the trick for you? To do this, simply gain access to the DialogContext object (its session scoped under key "dialog") and call stop(). Then get the DialogContextManager (session scoped under key Constants.MANAGER_BEAN) and call create(). TIA,
Sean
Craig
