It would help me to see a description of the problem that you people are trying to solve as you kick around various solutions. Solutions to what?
I've never had that problem, you see, so there is an important sense in which I do not know what you are talking about. I'd like to know.
Thanks to anybody who can slow down to explain.
To make Java suitable and widely popular for making decent web applications, for both novice and advanced users, we need
(1) The ability to have structure from an object and control-flow point of view, not a mess of spaghetti and ad-hoc control flow. This is very hard to do right now because of lack of a single point of control and previous ad-hocery.
Struts has been the most widely used answer up to now (and there are others certainly), but it has not been officially blessed as part of the Java standards, so some people are not even aware of it.
(2) Rich components for use in page-composition tools by less-experienced users. Above all else, we need a decent and easy-to-use data grid component to access an present database data. .Net has it and a lot of people will throw Java overboard unless it has too soon.
(3) Enough commonality that it is not all different in every Java vendors' tools.
I think Java Server Faces (with Struts initially) is the best hope for solving (1) and (2). They may have messed up on (3), but hopefully that will be repairable later on.
Some think we should just stick with Struts though, and address the need for rich components another way....
Don
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
