Hi Tom, I went down the same path as you with the gdata library and I was going to take a look at this library, which the developer claims does work on Android:
http://code.google.com/p/simply-gdata/ I'd be interested in if this works for you, as I haven't gotten around to looking at it and if it solves my medium-term needs. On Mar 15, 10:00 am, Tom <[email protected]> wrote: > Thanks everyone for all of your suggestions. I haven't been able to > get the com.google.gdata classes to load properly in the emulator or > my N1 phone. > > The stack trace indicates that the DVM cannot load classes in the > com.google.gdata.client packages, despite the jars being included in > the Eclipse project. My test app generates the following messages when > trying to instantiate a > com.google.gdata.client.calendar.CalendarService object: > > W/dalvikvm( 220): Unable to resolve superclass of Lcom/google/gdata/ > client/ca > lendar/CalendarService; (6) > W/dalvikvm( 220): Link of class 'Lcom/google/gdata/client/calendar/ > CalendarSe > rvice;' failed > E/dalvikvm( 220): Could not find class > 'com.google.gdata.client.calendar.Cale > ndarService', referenced from method > com.tomoreilly.CalendarTest.onCreate > W/dalvikvm( 220): VFY: unable to resolve new-instance 15 (Lcom/google/ > gdata/c > lient/calendar/CalendarService;) in Lcom/tomoreilly/CalendarTest; > D/dalvikvm( 220): VFY: replacing opcode 0x22 at 0x0012 > D/dalvikvm( 220): Making a copy of Lcom/tomoreilly/ > CalendarTest;.onCreate cod > e (608 bytes) > W/dalvikvm( 220): Unable to resolve superclass of Lcom/google/gdata/ > client/ca > lendar/CalendarService; (6) > W/dalvikvm( 220): Link of class 'Lcom/google/gdata/client/calendar/ > CalendarSe > rvice;' failed > I/dalvikvm( 220): Could not find method > com.google.gdata.client.calendar.Cale > ndarService.setUserCredentials, referenced from method > com.tomoreilly.Calendar > Test.onCreate > W/dalvikvm( 220): VFY: unable to resolve virtual method 46: Lcom/ > google/gdata > /client/calendar/CalendarService;.setUserCredentials (Ljava/lang/ > String;Ljava/ > lang/String;)V > D/dalvikvm( 220): VFY: replacing opcode 0x6e at 0x0025 > W/dalvikvm( 220): Unable to resolve superclass of Lcom/google/gdata/ > data/cale > ndar/CalendarFeed; (20) > W/dalvikvm( 220): Link of class 'Lcom/google/gdata/data/calendar/ > CalendarFeed > ;' failed > > I haven't been able to solve this specific problem, but instead have > decided to take the alternate approach suggested by Jim Blackler > athttp://jimblackler.net/blog/?p=151. His approach does not rely on > com.google.gdata classes, but instead uses an Intents mechanism that > is not documented by Google. > > Regards, > Tom > > On Mar 14, 12:37 am, Bob Kerns <[email protected]> wrote: > > > > > Yes. The reason I do copy them (and recommend copying them) to a lib/ > > directory is twofold: > > > 1) It makes them an explicit part of your project for versioning. If > > you use Subversion you can make these be a copy from a directory of > > third-party components. You could copy the third-party directory for > > tagging as well as your project, but this makes the dependency more > > apparent. > > > 2) It's compatible with how the ant build scripts are set up out-of- > > the-box, so it makes it easier to transition to an ant-based > > production build. > > > But as you note, Eclipse doesn't really care. > > > On Mar 13, 9:14 pm, Kumar Bibek <[email protected]> wrote: > > > > It doesn't really matter if you create a lib folder and put the jars > > > and link them. It just works if you have added the jars the the build > > > path. Though I am not able to figure out why you are getting this > > > error. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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/android-developers?hl=en
