I don't know what to say if you don't see the difference between a
page-centric view and a view that uses OOP principles.  Page-centric
talks about the Actions as if they were serving the pages.  The pages
are pages.  The Actions are Actions.


On Sat, 12 Mar 2005 11:43:39 -0800, Jesse Clark <[EMAIL PROTECTED]> wrote:
> Oops, as I had said in the paragraph that got snipped out, I am still
> trying to figure out the best way to fit everything together and
> obviously I misunderstood your comment to Joel.
> 
> I am very interested to learn more about how to approach struts
> application design in a less page centric manner. Could you point me to
> some resources that could help me understand the alternate approach that
> you recommend?
> 
> TIA,
> -Jesse
> 
> Dakota Jack wrote:
> 
> ><SNIP>
> >On Fri, 11 Mar 2005 12:09:25 -0800, Jesse Clark <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Joel,
> >>
> >>Here is a short description from the FAQ that starts to describe the
> >>alternative that Jack mentioned below:
> >>http://struts.apache.org/faqs/newbie.html#prepopulate.
> >>
> >>This approach basically means that you end up with two actions per
> >>form/jsp which will increase your maintenance work a little but it
> >>provides clean entry points into the work flow and clearly illustrates
> >>what responsibilities an action has by its naming scheme.
> >>
> >>
> ></SNIP>
> >
> >This is definitely not what I am talking about.  This is a
> >page-centric perspective that I am suggesting is not helpful.
> >
> >What I am talking about does not use multiple actions per form.  There
> >is no increase in maintenance at all.
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to