IMO depends on how much customization you want to do. If you want to add a rewriter to the beginning or end of the rewriter chain you might just be able to extend RewriteModule. We @Google have enough customization that we basically just created our own RewriteModule and in it supply our own bindings in the order we require. We don't get as much code reuse this way (ie. we don't use Shindig's RewriteModule) but we get more flexibility.
Cheers, John On Tue, Dec 21, 2010 at 12:59 PM, NikNik <[email protected]>wrote: > hi > > I have a small question because I'm newbie in Guice. > > Where is the best place to inject my additional GadgetRewriter > implementation ? > I mean which module I should replace or where add provider/module or ... > if I don't want to harm whole architecture ? > > Should I replace/extend DefaultGuiceModule and RewriteModule? > Or better way to provide new module for GadgetRewritersProvider injection ? > > I just want to keep the shindig clear like it is :) > > thanks >
