I didn¹t say that it *wouldn¹t* work, just that its tied to lift-webkit... Besides, he says that he will be doing a lot of data intensive processing - seems like JPA would play better there as Mapper is usually has a ceiling of functionality and then it becomes necessary to move to JPA anyway. IMHO, might as well save the recoding time and just work with JPA right away if he knows from the start that he will have tricky data ORM tasks.
Cheers, Tim On 23/06/2009 18:28, "Jorge Ortiz" <jorge.or...@gmail.com> wrote: > I've used Mapper in desktop apps too. It works fine. > > --j > > On Tue, Jun 23, 2009 at 9:56 AM, Naftoli Gugenhem <naftoli...@gmail.com> > wrote: >> >> I used mapper in an offline (demo) app. You have to include the util and http >> jars IIRC but it's a desktop app. If you're subcribed to scala-user, I posted >> it (I think last week) in the thread about a scala SWT DSL. >> >> ------------------------------------- >> Timothy Perrett<timo...@getintheloop.eu> wrote: >> >> >> Hi Joe, >> >> Mapper does not work standalone, its not like ActiveRecord in that >> sense - its tied to lift-webkit. Your best bet would be to go with >> JPA; I think that will serve you better anyway. >> >> Cheers, Tim >> >> On Jun 23, 4:47 pm, Joe Wass <j...@folktunefinder.com> wrote: >>> Good afternoon (at least in England), >>> >>> I'm writing an application which has a significant Lift manifestation, >>> but also some stand-alone Scala (maybe even Java but I'll exclude this >>> from the conversation). The stand-alone code is a set of tools that >>> hang off the database and do some heavy-lifting with the data in the >>> database, out of sync with the site. Something like periodic data- >>> crunching from the data on the site. The question comes down to >>> database mapping. >>> >>> I was wondering what people think is a sensible way of doing this. My >>> data model is simple enough that Mapper could work and I could use the >>> same classes. I'm aware there are many different ways I could do it, >>> but it would be nice to do it that way for the sake of simplicity. >>> >>> Does this sound a sensible approach? Has anyone else written an app >>> that's half online, half offline? Are there any obvious pitfalls? >>> >>> Cheers >>> >>> Joe >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
