The major problem on Servlet Container remains a problem. A Decent exception handling flow. This is on the strong points of AOP and Spring. I just take a look on now on Guice, seems the light one is not more so light. This is the major problems of 'components'. The thing don't stop to grow, the bugs too. At counter part, the histories remains the same.
Usually you need to consume or expose a service, on both cases you will have to build a protocol, sucessive requests, responses, i haven't see the need to fat components to do this, just programming and testing. Companies spend like zillions on legacy systems intead to mount a pool of programmers, then component after component born, and if they really solved the problem, the version 1 could be enough.
But this is not what happen, so you lost the programmer and enter on scene, the 'fat component', the silver bullet that can costs some millions, by the end, be replaced by another version. A typical example is spring and struts, both were good until last versions, usually when the owner of the idea stop to take care of it's sollution such things happens. Another example, hibernate, same thing.
For example annotations, 10% of the programmers means what means annotation in Servlet life cycle, 5% know what happens on aspect programming, but 80% of them use it. And what is more important at end tha t is organize the styling, using a strong verification is left at side. Is where enters sitemesh, and why to not use too much components, let the progamming with a lot of standards, few use cases and styling porking, Blog is the best example. The most suine styling constructed by a human been. They could be executed, their pieces distributed between famine dogs.
What is more nice is all, the configuration, styling can be put inside a database, ,mainly on appengine, that avoid all 'SQL' problems, who likes SQL does not belongs to Knut family, is another gen, another spiece on tree. Procedure monkeys.
