On 1/2/07, Adam Koch <[EMAIL PROTECTED]> wrote:
I'm working with the latest snapshot and to get out of a sub-dialog, I have to hit the "Cancel" (or "Finish") twice to return to the previous dialog. Has anyone else seen this? I thought it might be my dialog-config.xmlwasn't set up correctly, but I compared it to the one from this article[1] and it seemed fine. Is this perhaps a new bug with the latest version?
The dialog definition looks reasonable (although there is an emerging best practice of not using embedded spaces in state identifiers), so there might be some issue in the pages themselves. Quick things to check: * Do you have immediate="true" on your cancel button? You'll probably want this, because it bypasses validation that is generally unwanted if you're cancelling out of a transaction. * Do you have a messages component on the page to see if any validation or conversion errors are actually happening? This is a common bugaboo for JSF developers, even if not using the dialog infrastructure, because such errors take precedence over the normal navigation of a non-immediate command or hyperlink. If this doesn't help, another way to delve more deeply into what is going on is to turn up logging to the trace level (Shale DIalog uses Commons Logging for this) on a logger named " org.apache.shale.dialog.basic.BasicDialogContext" to get a pretty copious description of what is actually happening inside the dialog engine -- it might provide some clues about what is actually going on. Thanks,
Adam
Craig
