When we were asked to use a Client developed web framework (where in you just need to configure a few entries in some configuration file and lo and behold the required methods get called ) I was baffled and intrigued by the working of the web frameworks.

The most common features of a web framework is the master controller servlet model and the request to form bean bindings.

Its now that i realise how these things can be built from scratch by anyone using the reflection apis provided by java.

As a matter of fact i have already developed the controller model program on lines with struts and the auto formbean binding mechanism.

I am looking out for some real suggestions with regards to some peculiar problems which j2ee developers expect of their web frameworks and some features that hasnt been explored so far...

Things which cud be highly configurable that could liberate users from thinking at the level of a servlet and concentrate at the higher level of fulfilling business requirements

any takers??

-karthik