RE: Action->Action flow

[Oron O Adam]

Hi Vjeran

Seems to me if you make your actions thin and put the logic in some joint
service class you will have 

Action a code 
{
        if(need to display screen)
        {
                setTemplate(additional screen)
        }
        else  // no need for screen
        {
                doService
                setTemplate(some final screen)
        }

}

Action b code
{
        doService()             
        settemplate(some final screen)
}

Oron

http://netada.co.uk

-----Original Message-----
From: Vjeran Marcinko [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 01, 2004 2:59 PM
To: [EMAIL PROTECTED]
Subject: Action->Action flow

Hi folks.

I have annoying problem with controling request flow in Turbine.
Few times I have come upon situation where some ActionA would need to check
will it forward request to ActionB or to some template (Screen) with form in
itself which when submitted will also call ActionB. In other words, this
ActionA decides will it skip page with form and execute ActionB directly.
But problem is that I cannot see the way to direct request from ActionA to
ActionB, because wherever I look, I just see examples with flow going from
Action->Screen and not Action->Action ?!
Is there some way to make it flow from Action to Action ?

Regards,
Vjeran


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]