Ryan Brown provided the solution: "I believe the problem is that you're using a property named 'model', but DataMapper::Resource already has a model method. I suspect it will work if you change the name of that property."
On Jun 6, 2:32 pm, Chris <[email protected]> wrote: > Hi Ted, > > That's a good idea. I actually found that code of yours through a > Google search and used it as a reference for connecting to the App > Engine datastore when I was creating my Rails app (thanks!). I'd be > happy to try your experiment but I'm afraid I'm not sure how to set up > a context in which to run your code. How are you running those tests? > My apologies if the answer should be obvious! > > No, I haven't tried uploading this code to the actual app engine. I'm > running my app with the dev appserver in Eclipse (via the Google > Plugin for Eclipse) - App Engine SDK is 1.2.1 / JRE6 System Library. > > Chris > > On Jun 6, 1:45 pm, Ted Han <[email protected]> wrote: > > > Hey Chris, > > > I find this quite peculiar. I've been using dm-appengine and haven't had a > > problem with it. I've even got a little test collection of models that i've > > set up (although i haven't finished off the specs entirely) > > here:http://github.com/knowtheory/dm-appengine-tests/ > > > Can you tell me if you can pull those down and create an > > Eye.create(:color=>"green") locally? > > > Actually, that's the other question i should ask. Are you encountering this > > problem locally? or up on the actual app engine? > > > -Ted (knowtheory) > > > On Sat, Jun 6, 2009 at 12:34 PM, Chris <[email protected]> wrote: > > > > Hi Kristian, > > > > Yes. I'm using the latest trunk of appengine-apis-0.0.4 and the dm- > > > appengine-0.0.1 gem to talk to DataMapper (0.10.0) on App Engine via > > > JRuby (1.3rc) on Rails. I thought this configuration was compatible. > > > > I was hoping someone familiar with DataMapper might notice something > > > I'm doing wrong in how I'm using DataMapper. If my use of DataMapper > > > seems ok, then, as you suggested, maybe this is a problem with dm- > > > appengine - perhaps with the way it is trying to translate the > > > DataMapper model into its equivalent Java representation for App > > > Engine. Unfortunately I can't replace dm-appengine with another > > > adapter and without it I can't use Datamapper and have to write my > > > models directly in Java - not something I wanted to do. But perhaps I > > > don't have a choice. > > > > Thanks for taking a look, > > > Chris > > > > On Jun 6, 11:29 am, kristian <[email protected]> wrote: > > > > it seems to be more of dm-appengine problem. did you use the lastest > > > > build for dm-code/dm-appegine ? > > > > > see alsohttp://code.google.com/p/appengine-jruby/source/detail?r=59 > > > > > On Jun 6, 6:40 am, Chris <[email protected]> wrote: > > > > > > I'm using the appengine-apis and dm-appengine gems to talk to > > > > > DataMapper on App Engine via JRuby on Rails. > > > > > > When I try to save an instance of my Car model, I get an error saying > > > > > that "org.jruby.RubyClass is not a supported property type". The full > > > > > trace is here:http://pastie.org/502404 > > > > > > The Car model is basic: > > > > > > class Car > > > > > include DataMapper::Resource > > > > > > property :id, Serial > > > > > property :make, String > > > > > property :model, String > > > > > end > > > > > > And the Controller does very little beyond generic scaffold logic and > > > > > trying to save an initial Car to the datastore: > > > > > >http://pastie.org/502400 > > > > > > This is my Environment.rb file: > > > > > >http://pastie.org/502405 > > > > > > Any feedback would be appreciated. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
