Please see http://blog.lostlake.org/index.php?/archives/19-Keeping-the-meaning-with-the-bytes.html
On Sat, May 16, 2009 at 9:10 AM, Rob H <[email protected]> wrote: > > Hi, > > I'm evaluating Scala and Lift for a new project and in reading through > the "Getting Started" guide, I noticed that the ORM approach in Lift > seems to involve weaving persistence code directly into the entity > classes (LongKeyedMapper, MappedLongForeignKey, etc.) and companion > objects. It's an interesting design choice because the trend in other > frameworks is toward an intentional separation of concerns: POJOs as > entities, DAOs for persistence. Spring and Seam with Hibernate/JPA > come to mind. Could someone explain the reasoning behind Lift's take? > I don't mean to pass judgment, just trying to understand the > motivation. > > Thanks. > -Rob > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
