Accessing a nested page flow directly

["Cannon-Morrett, Lisa L" <li...@hp.com>]

Hi,

I have a nested page flow that is a login to the application.  The user
is also allowed to access the login page flow directly. In this case, if
the login is successful, I'd like to direct them to the application's
main page. Is there a recommended approach to handling a nested page
flow that may not always be nested?

Lisa 

Re: Accessing a nested page flow directly

[Carlin Rogers <cr...@bea.com>]

Yes. Thanks for adding the code snippet!

Richard Feit wrote:

> So would the entire class be something like this (where "loginSuccess" 
> is the return action from /login/Login.jpf)?
> 
>    @Jpf.Controller(
>        simpleActions={
>            @Jpf.SimpleAction(name="begin", path="/login/Login.jpf"),
>            @Jpf.SimpleAction(name="loginSuccess", 
> path="/home/Controller.jpf)
>        }
>    )
>    public class LoginStandalone extends PageFlowController
>    {
>    }
> 
> Rich
> 
> Carlin Rogers wrote:
> 
>> Hi Lisa,
>>
>> How are user going directly to your login page flow directly?
>> Is it from a link off of the app?
>>
>> Maybe one way to do this is to create a page flow that is
>> sort of a wrapper for the nested login page flow. The wrapper
>> is what you expose to the customer and it forwards to
>> the nested login page flow. The login page flow can remain
>> completely modular/independent. The wrapper page flow
>> would just have some SimpleActions and could return to
>> the main page.
>>
>> Just a thought,
>> Carlin
>>
>>
>> Cannon-Morrett, Lisa L wrote:
>>
>>> Hi,
>>>
>>> I have a nested page flow that is a login to the application.  The user
>>> is also allowed to access the login page flow directly. In this case, if
>>> the login is successful, I'd like to direct them to the application's
>>> main page. Is there a recommended approach to handling a nested page
>>> flow that may not always be nested?
>>>
>>> Lisa
>>
>>
>>
>>
> 

Re: Accessing a nested page flow directly

[Richard Feit <ri...@bea.com>]

So would the entire class be something like this (where "loginSuccess" 
is the return action from /login/Login.jpf)?

    @Jpf.Controller(
        simpleActions={
            @Jpf.SimpleAction(name="begin", path="/login/Login.jpf"),
            @Jpf.SimpleAction(name="loginSuccess", 
path="/home/Controller.jpf)
        }
    )
    public class LoginStandalone extends PageFlowController
    {
    }

Rich

Carlin Rogers wrote:

> Hi Lisa,
>
> How are user going directly to your login page flow directly?
> Is it from a link off of the app?
>
> Maybe one way to do this is to create a page flow that is
> sort of a wrapper for the nested login page flow. The wrapper
> is what you expose to the customer and it forwards to
> the nested login page flow. The login page flow can remain
> completely modular/independent. The wrapper page flow
> would just have some SimpleActions and could return to
> the main page.
>
> Just a thought,
> Carlin
>
>
> Cannon-Morrett, Lisa L wrote:
>
>> Hi,
>>
>> I have a nested page flow that is a login to the application.  The user
>> is also allowed to access the login page flow directly. In this case, if
>> the login is successful, I'd like to direct them to the application's
>> main page. Is there a recommended approach to handling a nested page
>> flow that may not always be nested?
>>
>> Lisa
>
>
>

Re: Accessing a nested page flow directly

[Carlin Rogers <cr...@bea.com>]

Hi Lisa,

How are user going directly to your login page flow directly?
Is it from a link off of the app?

Maybe one way to do this is to create a page flow that is
sort of a wrapper for the nested login page flow. The wrapper
is what you expose to the customer and it forwards to
the nested login page flow. The login page flow can remain
completely modular/independent. The wrapper page flow
would just have some SimpleActions and could return to
the main page.

Just a thought,
Carlin


Cannon-Morrett, Lisa L wrote:

> Hi,
> 
> I have a nested page flow that is a login to the application.  The user
> is also allowed to access the login page flow directly. In this case, if
> the login is successful, I'd like to direct them to the application's
> main page. Is there a recommended approach to handling a nested page
> flow that may not always be nested?
> 
> Lisa 
>