Re: DAO with EOF
Christian Edward Gruber <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.devel |
|---|---|
| Message-ID | <[email protected]> |
The pattern exists because people wanted to better abstract and coordinate the crap they were producing in C++ and other languages. J2EE was built within the culture of those evolutions, but a lot of what happened with O/R frameworks in the smalltalk/objective-c era were largely ignored, because they were not popular. But you're right, the core pattern of a DAO is quite particular to the services-oriented approach that came from CORBA and the like. Christian. On 14-Nov-07, at 12:24 PM, Daryl Thachuk wrote: > > On 13-Nov-07, at 5:11 AM, Anders Peterson wrote: > >> Hi, >> >> I'd like to make my business objects independent of EOF. Thinking >> about doing doing this using the Data Access Object design pattern >> where the EOs are the DAOs and the BOs are POJOs. >> >> http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html >> >> Is (something like) this commonly done? Has anyone done it? >> >> /Anders >> > > Why would you want to do this? I think this pattern exists because > of limitations in J2EE. Limitations which do not exist in EOF. > > Of course I could be wrong :-) > > -daryl > > ------ > Daryl Thachuk > Montage Technologies Inc. > http://www.montagetech.com > > _______________________________________________ > WebObjects-dev mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/webobjects-dev