I think I need to elaborate on my thoughts some more, since I wasn't really clear the first time around...
A great deal has happened in web application framework land since Struts
came along 3-1/2 years ago.
new technologies:
bytecode manipulation
IoC
SOA
filters
xml (XML Beans?)
AOP (just to list all)
Oscar
Unit Testing
scripting (including client javascript)
XML-RPC (not really new, just I like )
JDK 1.4 (interesting quirk: should jericko use the poor JDK logger? Maybe, but it's poor.)
Some can be leveraged... others do not apply.
So, what makes Struts Struts? What characteristics do we need to preserve
in order to keep it Struts, and retain the greatness that has made it so
amazingly popular?
My answer is:
-light weight. If "jericho" is bloated, then IMO it fails.
-formbeans. The concept that bean properties correspond to a (html data entry) form. (thinking outside the box: maybe a XML Document that maps to form properties can also be a form bean in Jericho).
-it had several clear extension points
And what it did not have:
- A DAO. Many popular frameworks of the day went down with their DAO.
It was a minimalist framework, that did 80% of what you need and it did not get in the way when you wanted it to do things it was not designed for.
Therefore, one person needs to write most of Jericho over a single weekend and not try to please a committee, just their own business application and do initial check in! :-)
Lets not forget validation, btw. it should not be an after taught. Keep same? yes.
.V
"perfection is achived when you have nothing left to remove" by Saint something or other
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
