I've created a new WIKI page entitled "Shindig Spring Example": - http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
Can someone help me to get the source code into the svn sandbook space that Vincent mentioned? Then I can update the WIKI page w/ a link to the source code, so people can try out the example :) Cheers Chico 2009/2/11 Vincent Siveton <[email protected]> > Hi > > The wiki is definitely the best approach, a cookbook style could be a > good approach. > If you have some code, you could put it in a sandbok space in svn. > > Cheers, > > Vincent > > 2009/2/10 chico charlesworth <[email protected]>: > > Hi all, > > > > As you know shindig relies on guice as the preferred dependency injection > > framework, and that is all good. Yet we've gone with the approach of > using > > both spring and guice, simply because spring offers us great support for > JPA > > (e.g. transaction management) and AOP, and it's likely that we'll be > using > > other Spring features down the line. There has been a couple of > challenges > > in getting the project working nicely with these two technologies side by > > side, but we're fairly happy as things stand right now. Note that the > > integration doesn't include any changes to the shindig codebase, that is, > we > > still let shindig use guice as expected. > > > > My question to the community is, first and foremost, do you think this > would > > be beneficial to other people? And if so, what is the best approach in > > contributing the shindig/spring integration work we've done? > > > > At the minimum we would like to document this integration work and make > it > > available to the community, either in a WIKI or as a tutorial. Another > > approach would be to include the code in the samples module, but then I > > guess we would have to consider splitting the samples module into sub > > projects? > > > > Cheers, > > Chico > > >
