o:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 10:56 AM
To: Struts Users Mailing List
Subject: RE: best practice to avoid chaining actions
> -Original Message-
> From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 21, 2003 2:58 PM
> To: Struts Users Ma
03 10:56 AM
To: Struts Users Mailing List
Subject: RE: best practice to avoid chaining actions
> -Original Message-
> From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 21, 2003 2:58 PM
> To: Struts Users Mailing List
> Subject: Re: best practice to
> -Original Message-
> From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 21, 2003 2:58 PM
> To: Struts Users Mailing List
> Subject: Re: best practice to avoid chaining actions
>
>
>
>
> > Hello,
> >
> > If actio
> Hello,
>
> If action chaining is a design error, then the struts-example that
> comes with struts distributions has a design error, saveSubscription
> forwards to editRegistration.do!
>
> Anyway, what I do is keep validation off action classes, by moving
> them off to action forms using validat
: Struts Users Mailing List
Subject: best practice to avoid chaining actions
Hi all,
I've read on this list that chaining actions is considered as a design
error.
On the project I'm working on, some developers need to make some business
validation on a form before going to the next
Hi all,
I've read on this list that chaining actions is considered as a design error.
On the project I'm working on, some developers need to make some business validation
on a form before going to the next
page. This validation occurs in an Action class, let's say Action1.
It's true.
In case you have coarse grained ActionForm which is used by BOTH actions
in that case reset() will be called twice as request will go from
RequestProcessor both times.
Theoretically, in case you have DIFFERENT ActionForms for BOTH actions
in that case reset() will be called for re
Hello everybody,
I cannot understand the following passage from Ted Husted's Struts in
Action (p.228):
"If you forward from one Action to another Action... the ActionForm
bean is reset, repopulated, and revalidated, and, if all goes well,
passed to the second Action"
How can the same ActionForm
Try forward as follows
Ashutosh Satyam wrote:
Hi,
I just wanted to know how do I chain the actions, if the action classes sit in
separate struts-config file.
The two struts configuration files are as mentioned below.
Struts-configApp1.xml
type="com.test.Operation"
scope="request"
Hi,
I just wanted to know how do I chain the actions, if the action classes sit in
separate struts-config file.
The two struts configuration files are as mentioned below.
Struts-configApp1.xml
Struts-configApp2.xml
Snippet of the web descriptor file.
actio
Hopefully someone can advise me how to get round this.
Essentially I have an action that prepares a page, then forwards to a jsp. The
jsp submits back to the same action, the action carries out certain operations
dependant upon a hidden flag, then if necessary forwards on to another action,
o
> I have encountered this problem before. Try this:
> Within your first Action set the get the values that are not
> being passed from the request object. Then before forwarding
> to the next Action set these values explicitly in the request
> objects attributes.
My current method is to use a
Olivier [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 12:43 PM
To: 'Struts Users Mailing List'
Subject: RE: Loosing form data when chaining actions
> >>>Hi,
> >>>
> >>>I defined 2 actions in session scope referring the same
> &
> >>>Hi,
> >>>
> >>>I defined 2 actions in session scope referring the same
> >>>
> >>form. The first
> >>
> >>>action sets some properties in the form and then forwards
> >>>
> >>the request to the
> >>
> >>>second action. The second action sets some more properties
> >>>
> >>and then forwards
ROSSEL Olivier wrote:
Hi,
I defined 2 actions in session scope referring the same
form. The first
action sets some properties in the form and then forwards
the request to the
second action. The second action sets some more properties
and then forwards
to a JSP page which contains the
> > Hi,
> >
> > I defined 2 actions in session scope referring the same
> form. The first
> > action sets some properties in the form and then forwards
> the request to the
> > second action. The second action sets some more properties
> and then forwards
> > to a JSP page which contains the htm
On Tue, 3 Dec 2002, [utf-8] Etienne Labonté wrote:
> Hi,
>
> I defined 2 actions in session scope referring the same form. The first
> action sets some properties in the form and then forwards the request to the
> second action. The second action sets some more properties and then forwards
> to
form data when chaining actions
1. make sure u are not creating a new instance of the form bean in the
second action and you have name attribute for both the action mappings(they
should be same, since u are using same form in both actions).
2. if you are going from the first action to the second
-
From: Etienne Labonté [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 4:11 PM
To: Struts Users Mailing List (E-mail)
Subject: Loosing form data when chaining actions
Hi,
I defined 2 actions in session scope referring the same form. The first
action sets some properties in the form and
Hi,
I defined 2 actions in session scope referring the same form. The first
action sets some properties in the form and then forwards the request to the
second action. The second action sets some more properties and then forwards
to a JSP page which contains the html form. The problem is only the
Hello,
I have a situation where I need to call an action and then following that action call
another one before doing an Action Forward to a JSP page.
From what I can tell there are various ways I could do this.
One is to simply specify this in the struts-config file ie
Hi,
There's been loads of discussion about how to implement this action
chaining..
Last night I cooked up yet another possible way to do it..
The chainToPage class implementation by Keith Bacon posted earlier
seemed like a nice way to do it at first.. But what I'm looking for is
a more generic w
-Original Message-
From: Oleg V Alexeev [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 27, 2001 3:53 PM
To: [EMAIL PROTECTED]
Subject: Re[2]: Passing parameters when chaining actions
Hello Fabien,
Friday, July 27, 2001, 11:29:06 PM, you wrote:
FM> Hello Oleg,
FM> Thanks for your help.
>
attributes gets you less overhead against query string.
FM> Thanks,
FM> -Fabien
FM> -
FM> Fabien Modoux,
FM> Voicemate - http://www.voicemate.com
FM> -Original Message-
FM> From: Oleg V Alexeev [mailto:[EMAIL PROTECTED]]
FM>
nt: Friday, July 27, 2001 2:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Passing parameters when chaining actions
Hello Fabien,
Friday, July 27, 2001, 8:02:28 PM, you wrote:
FM> I would like to have an action pass parameters
FM> to another actions using a forward action mapping.
FM> The sec
Hello Fabien,
Friday, July 27, 2001, 8:02:28 PM, you wrote:
FM> I would like to have an action pass parameters
FM> to another actions using a forward action mapping.
FM> The second action is configured with a form in
FM> the request scope:
FM> type="Action2Form"/>
FM>
I would like to have an action pass parameters
to another actions using a forward action mapping.
The second action is configured with a form in
the request scope:
I tried to have the first action instantiate
the form, populate it, and set it as a request
I have two Actions chained together and my appserver is
throwing core dumps on me left and right if I issue too
many repeat requests.
Here are the mappings:
So I have a jsp that shows a t
28 matches
Mail list logo
