[Lift] Re: JPA or JDO best for us on Google App Engine?
Its not so much running into problems, its just that JPA has some nice support and I was wondering if anyone was doing something similar for JDO. Channing --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
Yes I meant the ScalaJPA. Channing --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
Assuming that the PersistenceManager is thread-safe, it should be very easy
to crib from ScalaJPA to make a ScalaJDO. Off the top of my head:
import javax.jdo.PersistenceManager
trait JDOFactory {
protected def openPM () : PersistenceManager
protected def closePM (toClose : PersistenceManager) : Unit
}
trait ScalaPersistenceManager {
protected def pm : PersistenceManager
// define Scala-ish analogues for PersistenceManager, if needed
...
}
trait RequestVarPM extends JDOFactory with ScalaPersistenceManager {
object pmVar extends
RequestVar[PersistenceManager](openPersistenceManager()) {
this.registerGlobalCleanupFunc(ignore = closePM(this.is))
}
protected def pm = pmVar.is
}
Just a rough sketch, but that would allow you to do:
object Model extends RequestVarPM
And then have a per-request PersistenceManager
Derek
On Fri, May 22, 2009 at 12:38 PM, Channing Walton channingwal...@mac.comwrote:
Yes I meant the ScalaJPA.
Channing
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
cool, thanks for that. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
Has anything more been done with JDO support in Lift? I need to use JDO so it would help if there was some work being done on this. Channing --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
I don't have much experience with JDO, but I'm positive that if you run into issues you can find some help on the list. JDO is one area where we would appreciate notes from people who are working with it. If we get enough info, I could add another chapter to the book on JDO, similar to what we've done already for JPA. Derek On Thu, May 21, 2009 at 4:32 AM, Channing Walton channingwal...@mac.comwrote: Has anything more been done with JDO support in Lift? I need to use JDO so it would help if there was some work being done on this. Channing --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
Thanks David. That frees us up to choose JDO or JPA. 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. 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.comwrote: 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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
Thanks for the positive feedback on the book. If you have any critique of the content, please feel free to post it on the book group list: http://groups.google.com/group/the-lift-book As for JPA vs JDO I think you should have no problem going either route. I have no experience with JDO, so I can't comment there, but Scala has actually made JPA easier to use due to the availability of mixin traits and some type niceties. If you do go JDO I think we would all love to see any notes, stories, etc about your experience, and we could even build a JDO archetype if there is some scaffolding that would help people using JDO get a Lift app up and running quickly. Derek On Sun, Apr 12, 2009 at 4:42 AM, mal3 malcolm.gor...@gmail.com wrote: Thanks David. That frees us up to choose JDO or JPA. 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. 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 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
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. Mal. -- 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 -~--~~~~--~~--~--~---
[Lift] Re: JPA or JDO best for us on Google App Engine?
On Sat, Apr 11, 2009 at 10:21 PM, Oliver Lambert olambo...@gmail.comwrote: 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 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 -- 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 -~--~~~~--~~--~--~---
