On Sun, Apr 12, 2009 at 3:42 AM, mal3 <malcolm.gor...@gmail.com> wrote:
> > Thanks David. > > That frees us up to choose JDO or JPA. Yes. If you choose JDO, it'd be great for you to blog and/or send stuff to this list about how to do it. > > > PS: I've read the PDF of the Lift book and about half the PDF of your > Scala book. > I have to say the quality of writing and clarity of content is very > high. Thanks! Feel encouraged to blog your kind words, and critical feedback as well, about the books. APress, our publisher, loves community feedback... and I improve myself by hearing what other people think. Thanks! > And the > productivity of the authors is simply phenomenal. > > Mal. > > > On Apr 12, 3:27 pm, David Pollak <feeder.of.the.be...@gmail.com> > wrote: > > On Sat, Apr 11, 2009 at 10:21 PM, Oliver Lambert <olambo...@gmail.com > >wrote: > > > > > > > > > > > > > On Sun, Apr 12, 2009 at 2:54 PM, David Pollak < > > > feeder.of.the.be...@gmail.com> wrote: > > > > >> On Sat, Apr 11, 2009 at 8:36 PM, mal3 <malcolm.gor...@gmail.com> > wrote: > > > > >>> We are going to use the Google App Engine (GAE) for our app using GWT > > >>> with the new Google GWT Eclipse plugin support. > > > > >>> Our Scala and Lift skills are not up to the task of doing it in Lift > > >>> right now. > > >>> Once we have Exploring Lift and Beginning Scala books in our hot > > >>> little hands in May, we will begin to port the app over to Lift. > > > > >>> We need to choose between JPA and JDO. Which is the best choice > > >>> in anticipation of using Lift on GAE in a couple of months time? > > >>> So far as I can see, Lift supports JPA but not JDO. > > > > >> Lift supports either. Lift is persistence agnostic. Lift has a > module, > > >> mapper, that has JDBC support. Derek and Co. have built some nice > > >> JPA archetypes, but you can use JDO to your heart's content with Lift. > > > > > But there are no JDO examples while there are JPA and mapper ones. > > > > The issue is what Lift "supports". The HTTP request/response part of > Lift > > is agnostic about persistence. I made sure that this was the case. Use > of > > JPA in Scala/Lift was not well documented before Derek came along, but > it's > > quickly becoming the persistence mechanism of choice for Lift apps. > Perhaps > > if folks start using JDO with Lift, that will garner community support > and > > there will be a lot of JDO code that people contribute. > > > > So, I advocate using the persistence mechanism that one feels most > > comfortable with. I'll make sure that if folks start using JDO and they > > contribute JDO examples into the community that JDO gets the same level > of > > support as JPA and mapper. > > > > Thanks, > > > > David > > > > > > > > > > > > >>> Mal. > > > > >> -- > > >> Lift, the simply functional web frameworkhttp://liftweb.net > > >> Beginning Scalahttp://www.apress.com/book/view/1430219890 > > >> Follow me:http://twitter.com/dpp > > >> Git some:http://github.com/dpp > > > > -- > > Lift, the simply functional web frameworkhttp://liftweb.net > > Beginning Scalahttp://www.apress.com/book/view/1430219890 > > Follow me:http://twitter.com/dpp > > Git some:http://github.com/dpp > > > > -- 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
