Marius is working on the Record/Field stuff. The Record/Field stuff will replace Lift's mapper.
The Record/Field stuff will have pluggable persistence and maybe someone will plug JPA into it. On Fri, Oct 24, 2008 at 9:30 AM, Tim Perrett <[EMAIL PROTECTED]> wrote: > > Cheers guys, one thing though that confusses me about Dereks' JPA > example is why the JPA stuff wasn't consolidated into the lift > project? > > For instance, I understand why you might well want or need a separate > persistence tier in some applications or environments, but for the > majority of arbitrary applications, it seems to just make things more > complex / lengthy as you need to do "mvn install" all the time after > any updates. So far, having it consolidated seems to be going very > well 8-) > > Also, IMO, the Model.scala and JPA.scala should really have the > majority of there functionality taken out and put into the lift master > under say, net.liftweb.jpa.Helpers or something? It appears that the > functionality is so generic im copying and pasting a lot of the time > those files into different project :-( > > Cheers > > Tim > > > -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us 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 -~----------~----~----~----~------~----~------~--~---
