I've created a sample WAR application[1] which displays this behaviour.
If anyone is willing to download and run it I'd be very grateful!
Adam
[1] http://www.outofthemold.com/bwa.war
The view id was left off purposely so it would go back to the previous
dialog.
>-- Original message --
>From: "Adam Koch" <[EMAIL PROTECTED]>
>
> I added immediate="true" to my cancel button and added a messages tag to my
> page, but neither helped.
>
I wonder if you need a "viewId" attribute on the end state to tell it where to
go next? I didn'
I added immediate="true" to my cancel button and added a messages tag to my
page, but neither helped.
Here is some of the log after I clicked the Cancel button the first time:
[2007-01-02 12:47:35,160] [TRACE] [
org.apache.shale.dialog.basic.BasicDialogContext] [-->EndState()]
[2007-01-02 12:47:3
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'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.xml wasn't
set up correctly, but I compared it to the one from this article[1] and
