>Christian Schalk had a great tutorial for this -- it's a little out of date now, but the general concepts remain the same. We should probably try to get this included as a point of reference for the java deployment.
Yeah, sorry.. I got busy with various Google Developer Day events in Latin America and Asia, but after the weekend, I'll revamp all that stuff and make sure it's up to date again.. -Chris On Thu, Jul 3, 2008 at 10:35 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > On Thu, Jul 3, 2008 at 9:44 AM, Hans Granqvist <[EMAIL PROTECTED]> wrote: > >> Kevin: thanks. I followed some of the tutorials found online and >> they were all modifying the Guice java bindings file to point to their >> implementations, so I missed that web.xml actually decides which >> to use. > > > We just use web.xml to specify which module to load. You should never > modify the Guice modules that ship with Shindig -- instead, you should add > in your module and drop in the web.xml if the default wiring doesn't work > for you. > > >> >> I noticed Shindig pulls in something like 150 dependency jars. That's >> quite a lot. Like Andre hinted at, can we come up with a document >> with best practices to merge Shindig code with your own code? >> >> Not sure what format would be best: a simple readme.txt somewhere >> in the source tree? (I can post a simple patch to the list to get >> started, >> if we think that's the right way to do it) > > > Christian Schalk had a great tutorial for this -- it's a little out of date > now, but the general concepts remain the same. We should probably try to get > this included as a point of reference for the java deployment. > > >> >> Hans >> >> >> >> On 7/3/08, Kevin Brown <[EMAIL PROTECTED]> wrote: >> > On Wed, Jul 2, 2008 at 5:58 PM, Andre Lewis <[EMAIL PROTECTED]> >> wrote: >> > >> > > On Wednesday 02 July 2008 05:42:05 pm Kevin Brown wrote: >> > > > On Wed, Jul 2, 2008 at 4:00 PM, Hans Granqvist <[EMAIL PROTECTED] >> > >> > > wrote: >> > > > > This is all good info, thanks! >> > > > > >> > > > > However, I've looked into the source and have a few concerns. >> Here's >> > > what >> > > > > I'm struggling a bit with: >> > > > > >> > > > > I really want to use Shindig as a basis for my social network, >> but >> > > Maven >> > > > > is a lil bit too complex for me (hey, I struggle with Ant! ;). >> > > > > >> > > > > I'd like to be able to write my code on my own and then slot it >> into >> > > > > Shindig, but the SocialApiGuiceModule.java needs to be changed at >> > > > > compile-time, which means I somehow *have* to build my social >> network >> > > > > in one build. I therefore *have* to understand Shindig's build >> process. >> > > > >> > > > You're not supposed to modify the module, you're supposed to >> provide your >> > > > own. The module itself is actually loaded from the web.xml. You can >> > > always >> > > > replace SocialApiGuiceModule with any other module. >> > > >> > > Hey is this documented anywhere? >> > >> > >> > >> > This is how Guice works -- see the Guice user's guide for details. >> > >> > >> > > >> > > >> > > > >> > > > > Does this make sense? >> > > > > >> > > > > >> > > >> > >> > > -- Chris Schalk, Google Developer Advocate
