great, thx Vincent for setting that up! I don't yet have commit access though .. still eagerly awaiting for my account to be setup :)
can I email you the code Vincent, and ask you to commit it on my behalf to: https://svn.apache.org/repos/asf/incubator/shindig/sandbox /shindig-spring-example/trunk Cheers Chico 2009/2/17 Vincent Siveton <[email protected]> > Hi Chico, > > <Sorry for the delay.> > > Now that svn is up, I created a sandbox space in svn [1]. I guess that > you could create a new folder/project for your code. > > Cheers, > > Vincent > > [1] https://svn.apache.org/repos/asf/incubator/shindig/sandbox > > 2009/2/17 chico charlesworth <[email protected]>: > > Does anyone know of a svn scratchpad space that would be suitable to put > > example shindig code? > > > > Failing this, is it best instead to attach any such example source code > to > > the WIKI .. not ideal but might be ok for the interim? > > > > Cheers > > Chico > > > > 2009/2/16 Ian Boston <[email protected]> > > > >> Chico, > >> Could you ask the question on list, everyone should be a part of the > >> discussion, you never know some one might have an unexpected gem on the > >> subject :) > >> Thanks > >> Ian > >> > >> On 16 Feb 2009, at 22:40, chico charlesworth wrote: > >> > >> Hi Vincent, > >>> > >>> Can you point me to the svn sandbook space that you mentioned .. I > think > >>> we all agree that it would be nice to have a standard place to put > example > >>> code, but Ian says he doesn't think that shindig has such a scratchpad > place > >>> (see below)? > >>> > >>> Failing this, I can just attach the example source code to the WIKI > page > >>> .. not ideal but might be ok for the interim? > >>> > >>> Cheers > >>> Chico > >>> > >>> 2009/2/16 Ian Boston <[email protected]> > >>> Chico, > >>> I think some projects have a scratchpad space which is probably along > side > >>> trunk but not trunk. > >>> > >>> AFAIK, Shindig doesn't have one. > >>> > >>> I would bring it up on the list, as there may be a more standard place > to > >>> put it, and Vincent would certainly know.... sounds like a good idea to > me > >>> and reduces the effort levels required maintianing it. > >>> > >>> Remember, that committing anything into trunk comes with it a > commitment > >>> to nurture the committed code, and if its part of the trunk, then that > can > >>> be a pain. > >>> > >>> Ian > >>> > >>> > >>> On 16 Feb 2009, at 14:25, chico charlesworth wrote: > >>> > >>> Hi Ian, > >>> > >>> Any idea where this svn sandbook space might be that Vincent mentioned? > By > >>> any chance have you got commit access to it? > >>> I could just attach the spring example source code to the wiki page, > but > >>> would of course be best placed in svn so that it can be regularly > updated to > >>> keep in synch w/ shindig. > >>> > >>> Cheers > >>> Chico > >>> > >>> 2009/2/13 chico charlesworth <[email protected]> > >>> 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 > >>> > > >>> > >>> > >>> > >>> > >>> > >> > > >
