The important thing to remember is that Impala is not a web framework as
such, rather a dynamic module framework. Using Impala doesn't affect the
architecture of a Spring MVC application.
There's a brief description in this interview:
http://osgi.dzone.com/articles/impala-alternative-module
Also, there's quite a lot more detail in the slides:
http://impala.googlecode.com/svn/wiki/presentations/tss-europe.pdf (take
a look for example in the "Under the Hood" section).
When I get some time I hope to supplement the wiki with some more
written documentation.
A couple of other useful links:
http://code.google.com/p/impala/wiki/ModuleReloading: describes the
mechanism for module reloading
http://code.google.com/p/impala/wiki/ModuleStructure: describes the
structure of a particular project
http://code.google.com/p/impala/wiki/WebModuleBasedHandlerRegistration:
describes how multi module structure works for web applications
If there are specific areas where you think documentation will help,
that would be helpful ...
Cheers,
Phil