If you are just presenting data to the user, then I would say just go
ahead and use the model beans. The one thing to watch for is whether
there are any properties that call back to the model. If there are, you
need to make sure that everyone writing a presentation page that uses
this bean knows
I'm in the process of converting a webapp to using struts, am trying to
use best practices to make sure that I keep presentation split from
business, and I was wondering what all of you experts do to handle the
data transition from model business logic beans to the presentation.
As I see it, I
On Wed, 19 Mar 2003 14:46:41 -0600
Kirby Vandivort [EMAIL PROTECTED] wrote:
So, I guess my question is... is there a consensus of any sort on how
this should be done or, how do you do it, etc?
Unfortunately, I'm starting to find out more and more that there isn't a
consensus:) I'm also
On Wed, Mar 19, 2003 at 04:48:13PM -0500, Rick Reumann wrote:
On Wed, 19 Mar 2003 14:46:41 -0600
Kirby Vandivort [EMAIL PROTECTED] wrote:
So, I guess my question is... is there a consensus of any sort on how
this should be done or, how do you do it, etc?
Unfortunately, I'm starting to
-
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2003 3:48 PM
To: Struts Users Mailing List
Subject: Re: Design philosophy, beans, model to view
On Wed, 19 Mar 2003 14:46:41 -0600
Kirby Vandivort [EMAIL PROTECTED] wrote:
So, I guess my question
5 matches
Mail list logo
