Re: Using Design Patterns ???
Re: Using Design Patterns ???
- Subject: Re: Using Design Patterns ???
- From: Art Isbell <email@hidden>
- Date: Sat, 22 Mar 2008 13:28:04 -1000
On Mar 22, 2008, at 12:17 PM, Gustavo Pizano wrote:
To Use or not TO use Design pattern??.... I mean should I implement
something like a DAO which will be in charge to communicate with
EO's, or should I make this directly from the .java of the
components.??
WO encourages the Model-View-Controller design paradigm. WO apps are
server processes, so the concept of View objects is a bit odd. But
the WO framework does generate HTML that Web browsers display as user
interface objects on Web pages, so I suppose WOElements could be
considered View objects. WO developers don't need to create
WOElements very often. Instead, WO developers interact with
WOElements in WOD files and HTML templates.
EO's are Model objects that know nothing about Web pages themselves.
All business logic should be implemented in these EO classes. So this
is where the bulk of your real logic should be.
I consider WOComponents to be Controller objects because they are the
glue between Model (e.g., EO's) and View (e.g., WOElements) objects.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden