On Mon, Jan 24, 2011 at 12:32 PM, Igor Vaynberg <[email protected]> wrote: > > with the new split we have introduced iprovider interface which > decouples the mess. a good example is that if now some part of request > processing needs a configurable option it gets it via iprovider which > in turn gets it from an application setting. this allows us to unit > test that part of code without requiring the application to be set up > and thus without requiring wicket tester. >
It sounds like you've fixed some of the problem(s) that caused you to split stuff up in the first place, but you did it using *code design* which is the correct way to go about this. The "module gymnastics" approach just leads to confusion, IMHO.
