ce.
Filters aren't a parallel system to Struts because they logically sit in
front of Struts handling requests before Struts gets them.
David
From: Thorin Linderholm <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: 'Struts Users Maili
C where there is a 'view' controller and 'buisness'
>> controller
>> (which seems a bit redundant to me.)
>
> Well, at one point you will wonder which is more cumbersome: coding
> Action classes or having a mile-long struts-config.xml.
>
> Paul
>
and 'buisness'
> >> controller
> >> (which seems a bit redundant to me.)
> >
> > Well, at one point you will wonder which is more cumbersome: coding
> > Action classes or having a mile-long struts-config.xml.
> >
> > Paul
> >
> >&
Mailing List' <[EMAIL PROTECTED]>
Subject: RE: design question about action chaining
Date: Tue, 1 Apr 2003 12:08:09 -0800
Filters are one of the design/imp choices I've considered under the
'parallel system' heading, though I hadn't thought of trying to use the
web
isness'
controller
(which seems a bit redundant to me.)
Well, at one point you will wonder which is more cumbersome: coding
Action classes or having a mile-long struts-config.xml.
Paul
-Original Message-
From: Paul Yunusov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2
s more cumbersome: coding Action
classes or having a mile-long struts-config.xml.
Paul
>
>
> -Original Message-
> From: Paul Yunusov [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 01, 2003 11:43 AM
> To: Struts Users Mailing List
> Subject: Re: design questi
esday, April 01, 2003 11:52 AM
To: [EMAIL PROTECTED]
Subject: Re: design question about action chaining
I think Filters would be a good choice for your needs. You can define a
filter for each piece of logic and then configure them in web.xml for groups
of pages. You'll need to put relat
I had come to the conclusion that Struts Actions are moreover 'View Adapter
Components' or "VAC's" (you can quote me on that one!) and should not be
relied on for handling business logic or data collection by any means, just
as a facsimile for "pulling" model/controller data into the view.
I wrote
re there is a 'view' controller and 'buisness' controller (which
seems a bit redundant to me.)
-Original Message-
From: Paul Yunusov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2003 11:43 AM
To: Struts Users Mailing List
Subject: Re: design question about action chai
I think Filters would be a good choice for your needs. You can define a
filter for each piece of logic and then configure them in web.xml for groups
of pages. You'll need to put related pages in the same path scheme so that
you can map a filter to the group instead of each page.
David
From
On Tuesday 01 April 2003 02:30 pm, Thorin Linderholm wrote:
> I have been tasked with porting an existing web application with it's own
> proprietary controller architecture to using Struts.
>
> As they are both web controller architectures, they have many similarities,
> but I'm running into one d
Thanks, Ted, for clarifying these issues for me.
> -Original Message-
> From: Ted Husted [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 02, 2003 11:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: design question about action chaining
>
>
> In Patterns o
In Patterns of Enterprise Application Architecture [1], Martin Fowler
[2] lays out two basic patterns for handling business logic [3].
* Transaction Script - "Organizes business logic by procedures where
each procedure handles a single request from the presentation.
* Domain Model - "An object mo
13 matches
Mail list logo
