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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
