Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41C1CE15.9010405@dbgroups.com>
Date: Thu, 16 Dec 2004 11:04:05 -0700
From: BaTien Duong <batien.duong@dbgroups.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
MIME-Version: 1.0
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: Commons Chain Cookbook: Why have Struts Actions?
References: <2004121513325.494124@pc18>
In-Reply-To: <2004121513325.494124@pc18>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ted Husted wrote:

>On Wed, 15 Dec 2004 17:22:15 +0000, Pilgrim, Peter wrote:
>  
>
>> I was thinking in truth, only providing access to the ``catalog''
>> and ``command'' not necessarily changing the execution model. But
>> if that is the case, could a Struts ``Action'' as it appears in
>> 1.2.6 actually be a commons chain `Command' type? If it is, then,
>> it opens the doors for the ``chaining action'' conundrum all again.
>>  
>>    
>>
>
>It's my own feeling that there should be a clean break between the presentation layer (Struts) that collects and display values, and the business logic layer (e.g. Chain) that should do everything else. 
>
>I started a new project this week based on Context, Command, and (as of five minutes ago) Spring. The paradigm is that the presentation layer collects whatever values are needed and puts them into a Context. A controller component executes the associated Command (or Chain) and returns the outcome in the Context. Both the Context and Command are extended so that they can handle all the business processing: Input and Output Validation, Execution, Error and Exception Handling, and Message Resolution. 
>
>For input, the Context has convenience properties for Locale, User, Role, and for output, there are properties for Output, Errors, Messages, and Fault (Exception). I expect there to be more, but I'm only adding what I need when I need it. 
>
>When the Context returns, it can be examined by the presentation layer, which can then display the output, messages, or errors.
>
>  
>
This is great Ted. What it means is that each individual backend 
software component catalog can determine finer grain of authorization 
and the amount of supplied information. The web layer will take care of 
the first pass and assemble the supplied fragments. Please let all the 
mortals know when it is available.

Thanks

BaTien
DBGROUPS

>It's all in C# now, since I'm working in .NET, but I'd like to port it back to Java 1.5 and maybe PHP 5. 
>
>-Ted.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
>
>
>.
>
>  
>


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