Shared Flow exception handling

[Jack Rudnick <ja...@compoze.com>]

When attempting to use a Shared Flow for exception handling, we
successfully have our handle redirect us to our "error" page.  On the
"error" page, we wish to have a "cancel" button, that will simply take
us back to the last point in our application before the exception what
generated.

 

It would seem that the correct way to do this would be to put a
"cancelAction" in the shared flow for the button to use that looks like
below:

 

@Jpf.Action( forwards = 

    {

    @Jpf.Forward( name = "success", 

        navigateTo = Jpf.NavigateTo.previousPage )

    } )

public Forward cancelAction

(

)

    {

    return new Forward("success");

}

 

This, however, does not seem to work.

 

Does anyone have any thoughts on how this should be done?

Re: Shared Flow exception handling

[Rich Feit <ri...@gmail.com>]

Hi Jack,

 From what you've posted, it looks like you need to forward to 
Jpf.NavigateTo.currentPage (not previousPage), which is the most recent 
page in the current page flow.  If that doesn't solve it for you, let me 
know.

Rich

Jack Rudnick wrote:

>When attempting to use a Shared Flow for exception handling, we
>successfully have our handle redirect us to our "error" page.  On the
>"error" page, we wish to have a "cancel" button, that will simply take
>us back to the last point in our application before the exception what
>generated.
>
> 
>
>It would seem that the correct way to do this would be to put a
>"cancelAction" in the shared flow for the button to use that looks like
>below:
>
> 
>
>@Jpf.Action( forwards = 
>
>    {
>
>    @Jpf.Forward( name = "success", 
>
>        navigateTo = Jpf.NavigateTo.previousPage )
>
>    } )
>
>public Forward cancelAction
>
>(
>
>)
>
>    {
>
>    return new Forward("success");
>
>}
>
> 
>
>This, however, does not seem to work.
>
> 
>
>Does anyone have any thoughts on how this should be done?
>
>
>  
>