you saying this is bad?
BAL
>From: "Andrew Hill" <[EMAIL PROTECTED]>
>Reply-To: <[EMAIL PROTECTED]>
>To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>Subject: RE: how to call more than one Struts Action for a given HTTP
>request
>Da
Message-
From: Mike Oliver [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 7:19 AM
To: 'Struts Users Mailing List'
Subject: RE: how to call more than one Struts Action for a given HTTP
request
I believe the best path for you on this is to SubClass the
RequestProcessor r
I believe the best path for you on this is to SubClass the
RequestProcessor rather than chaining. You could then use any number of
different design patterns to dispatch your actions and share data
between them or leverage the Workflow Extensions/State Engine.
Michael Oliver
AppsAsPeers LLC
7391 S
t; <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Subject: RE: how to call more than one Struts Action for a given HTTP
request
Date: Mon, 27 Jan 2003 20:25:04 +0800
You are referring to Action chaining?
This is
TED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 6:12 PM
Subject: RE: how to call more than one Struts Action for a given HTTP request
> Hi,
> If i understand u right u are saying that same request will be handled by more
> than one action..
> e.g. Some thing like if
Hi,
If i understand u right u are saying that same request will be handled by more
than one action..
e.g. Some thing like if user logs in, check his login credentials and then give
him the list of his accounts in a banjking app.So u wil like to have a
LoginAction(which just checks login) and a g
You are referring to Action chaining?
This is discouraged as it leads to all sorts of problems...
...but wheres the fun in that eh?
If you want to chain actions you can have the first actions actionForward
point at the next, etc...
Be aware that the RequestProcessor will repopulate the form from
7 matches
Mail list logo
