I’ve been worried for quite a long time. Robotlegs 1 was small and simple but a little difficult to extend. I wanted Robotlegs 2 to be flexible without becoming overly large or complex.
Timing
To extend any framework you need to be able to hook into that framework’s initialization process.
That Damned Context
The Robotlegs 1 context class was, to be frank, rubbish – it set defaults, configured dependencies and controlled initialization. Worse, to hook into the initialization process or change the defaults, users had to extend the class itself resulting in the proliferation of funny looking words like SignalDrivenCovariantlyMediatedModularShellContext. Continue reading
