Re: Using Design Patterns ???
Re: Using Design Patterns ???
- Subject: Re: Using Design Patterns ???
- From: Archibald Singleton <email@hidden>
- Date: Mon, 24 Mar 2008 13:17:27 -0300
On 22 Mar 2008, at 19:17, Gustavo Pizano wrote:
Hello, well, while developing my application, I came to fork. 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.??
WebObjects uses the MVC design pattern. My understanding is that the
model part is your EOModel, the controllers are your components .java
files and the views are your .wo / .html (inline bindings) files.
I'd recommend reading the legacy WO documentation (from WO 4.5.x) to
get a better understanding of the WebObjects from a architectural /
design pattern point of view. Even though the documentation is
outdated, it still provide valuable information that can't hardly be
found anywhere else.
http://developer.apple.com/referencelibrary/LegacyTechnologies/idxInternetWeb-date.html
In particular:
- WebObjects Developer's Guide
http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/Developer/WebObjects/DevGuide/DevGuideTOC.html
- EOF Developer's Guide
http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/Developer/EnterpriseObjects/DevGuide/GuideTOC.html
= tmk =
_______________________________________________
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