Dave, We did consider socialsite, yet we decided to go with shindig as we saw shindig as being a better fit to our needs. In saying that, I've looked at the JPA implementation in socialsite and it shares many similarities in the approach taken by the samples module in shindig. Since socialsite is using shindig already (by implementing PersonService, ActivityService, etc), it would be nice if they would contribute/merge their JPA implementation with shindig's. Has this idea been raised already, anyone?
Cheers Chico 2008/12/9 Dave <[EMAIL PROTECTED]> > On Tue, Dec 9, 2008 at 12:35 PM, chico charlesworth > <[EMAIL PROTECTED]> wrote: > > I worked on ActivityDb today and finally got it to persist - after fixing > > three bugs (see Jira-773 for more details). And ActivityServiceDb is in > not > > much better shape as it's looking rather bare at the moment. And of > course, > > no unit tests are yet covering these classes :) > > > > Is anyone else using the samples code as a basis for integrating a JPA > > persistence layer with shindig?! Surely someone who has got shindig up > and > > running with a decent persistence layer could contribute their code back > > into the project, rather than us newcomers having to struggle to create > and > > integrate our own? > > Project SocialSite includes a (JPA) persistent social graph and a > Shindig front-end, plus and API and widgets for friending, groups, > messages, etc. Source is available. It's dual licensed under > CDDL/GPLv2. > > http://socialsite.dev.java.net > > - Dave >
