You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Rajaneesh <ra...@slk-soft.com> on 2005/03/22 11:11:40 UTC

FW: Struts 1.3 chaining sequence

Hi,

  With respect to the previous versions of struts, we had the controller

1. instantiating & populating ActionForm,
2. Validating the fields in the action form,
3. Calling the execute method of Action
4. Getting the action forward from the execute method.



  With respect to Struts 1.3 are the same accomplished by (in the same
order)
1. AbstractCreateActionForm, AbstractPolulateActionForm
2. AbstractValidateActionForm
3. AbstractCreateAction, ExecuteCommand
4. AbstractPerformForward


  Could you please let me know if these are called by
ComposableRequestProcessor
and needs to be extended by the user?

Regards
Rajaneesh

-----Original Message-----
From: Ted Husted [mailto:ted.husted@gmail.com]
Sent: Tuesday, March 22, 2005 3:14 PM
To: Struts Users Mailing List; rajaneesh.acharya@slk-soft.com
Subject: Re: Struts 1.3 chaining flow diagram


Since Struts 1.3.0 doesn't exist yet :),  please redirect this post to
the DEV@ list.

-Ted.

On Tue, 22 Mar 2005 11:46:05 +0530, Rajaneesh
<ra...@slk-soft.com> wrote:
>
> Hi,
>
>   With respect to the previous versions of struts, we had the controller
>
> 1. instantiating & populating ActionForm,
> 2. Validating the fields in the action form,
> 3. Calling the execute method of Action
> 4. Getting the action forward from the execute method.
>
>   With respect to Struts 1.3 are the same accomplished by (in the same
> order)
> 1. AbstractCreateActionForm, AbstractPolulateActionForm
> 2. AbstractValidateActionForm
> 3. AbstractCreateAction, ExecuteCommand
> 4. AbstractPerformForward
>
>   Could you please let me know if these are called by
> ComposableRequestProcessor
> and needs to be extended by the user?
>
> Regards
> Rajaneesh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: FW: Struts 1.3 chaining sequence

Posted by Bill Siggelkow <bi...@bellsouth.net>.
You may want to take a look at 
http://www.onjava.com/pub/a/onjava/2005/03/02/commonchains2.html

-Bill Siggelkow

On 2005-03-22 05:41:40 -0500, "Rajaneesh" 
<ra...@slk-soft.com> said:

> 
> Hi,
> 
>   With respect to the previous versions of struts, we had the controller
> 
> 1. instantiating & populating ActionForm,
> 2. Validating the fields in the action form,
> 3. Calling the execute method of Action
> 4. Getting the action forward from the execute method.
> 
> 
> 
>   With respect to Struts 1.3 are the same accomplished by (in the same
> order)
> 1. AbstractCreateActionForm, AbstractPolulateActionForm
> 2. AbstractValidateActionForm
> 3. AbstractCreateAction, ExecuteCommand
> 4. AbstractPerformForward
> 
> 
>   Could you please let me know if these are called by
> ComposableRequestProcessor
> and needs to be extended by the user?
> 
> Regards
> Rajaneesh
> 
> -----Original Message-----
> From: Ted Husted [mailto:ted.husted@gmail.com]
> Sent: Tuesday, March 22, 2005 3:14 PM
> To: Struts Users Mailing List; rajaneesh.acharya@slk-soft.com
> Subject: Re: Struts 1.3 chaining flow diagram
> 
> 
> Since Struts 1.3.0 doesn't exist yet :),  please redirect this post to
> the DEV@ list.
> 
> -Ted.
> 
> On Tue, 22 Mar 2005 11:46:05 +0530, Rajaneesh
> <ra...@slk-soft.com> wrote:
>> 
>> Hi,
>> 
>> With respect to the previous versions of struts, we had the controller
>> 
>> 1. instantiating & populating ActionForm,
>> 2. Validating the fields in the action form,
>> 3. Calling the execute method of Action
>> 4. Getting the action forward from the execute method.
>> 
>> With respect to Struts 1.3 are the same accomplished by (in the same
>> order)
>> 1. AbstractCreateActionForm, AbstractPolulateActionForm
>> 2. AbstractValidateActionForm
>> 3. AbstractCreateAction, ExecuteCommand
>> 4. AbstractPerformForward
>> 
>> Could you please let me know if these are called by
>> ComposableRequestProcessor
>> and needs to be extended by the user?
>> 
>> Regards
>> Rajaneesh
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: FW: Struts 1.3 chaining sequence

Posted by Joe Germuska <Jo...@Germuska.com>.
At 3:41 PM +0530 3/22/05, Rajaneesh wrote:
>Hi,
>
>   With respect to the previous versions of struts, we had the controller
>
>1. instantiating & populating ActionForm,
>2. Validating the fields in the action form,
>3. Calling the execute method of Action
>4. Getting the action forward from the execute method.
>
>
>
>   With respect to Struts 1.3 are the same accomplished by (in the same
>order)
>1. AbstractCreateActionForm, AbstractPolulateActionForm
>2. AbstractValidateActionForm
>3. AbstractCreateAction, ExecuteCommand
>4. AbstractPerformForward
>
>
>   Could you please let me know if these are called by
>ComposableRequestProcessor
>and needs to be extended by the user?

You should not need to extend ComposableRequestProcessor unless you 
want to provide a custom implementation of ActionContext (and its 
possible that the mechanism for doing that may move out to a factory 
class; the issue has been raised but not discussed heavily.)

Regarding those commands, they are executed by the chain processing 
libraries, so that if you want to change that behavior, you should 
implement your own classes (possibly extending either the Abstract* 
commands or their concrete implementations in 
o.a.struts.chain.commands.servlet.*), and then specify them in a 
chain-config.xml file.  You can take the base chain-config.xml file 
from the struts-core.jar (or from 
http://svn.apache.org/repos/asf/struts/core/trunk/conf/share/chain-config.xml) 
and update it to your needs; then use the "chainConfig" servlet 
init-param (in web.xml) to point to your file, using either a 
servlet-context relative path or a classpath-relative path.

Joe

-- 
Joe Germuska            
Joe@Germuska.com  
http://blog.germuska.com    
"Narrow minds are weapons made for mass destruction"  -The Ex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org