The BeanWrapper and the BeanFactory are interesting ideas. An example of configuring commons DBCP is given http://www.springframework.org/docs/lightweight_container.html
I am not convince however of the requirement for BeanFactory. I can understand if you need to have massive XML configuration and need to dynamic generate Beans (objects) at run-time. It is great but other than that I can really view to the advantage inverse of control there that Struts or Commons BeanUtils combine Digester could not do itself.
I like this for beans: www.joda.org Wow! It would get rid of a lot of questions on the user list. (This man wanted to go ASF)
Struts is great because it concentrates on doing one thing well MVC. I wouldn't want it to branch out go into a generic framework space e.g Avalon, Expresso, Keel, Spring, Pico etc.
But maybe build Struts on top of Pico or similar (http://oscar-osgi.sourceforge.net) or hivemind or...
See if we pick high level light interfaces and use "generic" jars like now, it could be done quick like, and fund, since code would be done at a bit higher level.
(And maybe WebWork or Spring or .... implement our MVC high level light interface.)
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
