The client sends a request which is routed to an Action. The Action
confers with the business model and internal application resources to
select a response, and to generate any resources the response may need.
The resources are forwarded to the JSP view for rendering, often with
the help of internal application resources (shared with the actions).
Application resources include the Action Mappings and things like
connection pools. These resources are usually initialized from a
configuration file or servlet.
I mostly making a disinction between internal application resources,
like Action Mapping, and other portions of the business logic, which
might be shared with other applications. In a MVC environment, the
latter should not be accessed directly by the view.
Jonathan wrote:
>
> This is interesting, but Ted, how do I read this diagram??!
>
> ----- Original Message -----
> From: "Ted Husted" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 15, 2001 11:05 AM
> Subject: Re: Object Models and patterns in Struts
>
> > I'd say that this is a very clear expression of where most people are
> > trying to go right now.
> >
> > For my own work, I'd diagram the scenario as:
> >
> > Controller Model
> > App Layer Business Layer
> > HTTP +--------+ +------------------+
> > -------->| Action |<---->| Object Model |
> > Request +--------+ +------------------+
> > | ^
> > (Request Obj)| | +------------------+
> > | +-------<| App/Sess Objects | Controller
> > V v | - Action Mappings| App Layer
> > HTTP +--------+ | - Conn Pool |
> > <--------| JSP | | - et cetera |
> > Response +--------+ +------------------+
> > Web Layer ^
> > View |
> > [ Configuration ]
> >
> >
> > -- Ted Husted, Husted dot Com, Fairport NY USA.
> > -- Custom Software ~ Technical Services.
> > -- Tel 716 737-3463.
> > -- http://www.husted.com/about/struts/
> >
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
