On 19 Jul 2011, at 09:12, Jasha Joachimsthal wrote: > Amber looks promising but it doesn't provide a solution (yet) for storing > the actual keys and tokens. I'm first working on storing these objects to > replace the json files that Shindig currently uses.
Good point. I think there was a discussion on amber-dev about providing JPA beans for these a while back but it hasn't been implemented yet. > > On 19 July 2011 09:53, Scott Wilson <[email protected]> wrote: > >> Just a thought... Apache Amber (incubating) is heading towards a release >> soon - so should we be looking at using that in the future rather than >> maintaining a custom oAuth implementation? >> >> On 19 Jul 2011, at 08:29, Jasha Joachimsthal wrote: >> >>> I'm still working on storing OAuth information in the database (almost >> done >>> now). I see a difference in handling database objects/queries between the >>> rave-portal module and the rave-shindig module. >>> All rave-portal beans implement o.a.rave.portal.model.BasicEntity while >> all >>> rave-shindig beans implement >> o.a.shindig.social.opensocial.jpa.api.DbObject. >>> In rave-portal all classes that handle DB queries implement >>> o.a.rave.portal.repository.Repository and are configured through Spring. >> The >>> Repository implementations extend AbstractJpaRepository which supports at >>> simple CRD operations. The Repository implementations have test classes. >>> In rave-shindig there seems to be no common interface and injection is >> done >>> through Guice (the @Injects are commented out btw). Tests are missing. >>> >>> Is there someone who has time (and knowledge) to create a common basis >> for >>> database operations in both modules and set up tests for DB operations >>> rave-shindig? >>> >>> >>> Jasha Joachimsthal >>> >>> Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 >>> US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll >> free) >>> >>> www.onehippo.com >> >>
