JSF seems to be lightweight. It simplifies and speeds up development. So what limitations does it have? I don't know JSF (I must download it (and shale)), but it sounds like you've sacrificed the ability to deal with multiple Command scenarios (submit buttons) on a robust controller.
The last page I saw on my previous project had 10 submit buttons. What I see is developers writing monolithic tracts of code in their Action classes to handle all Commands at once. E.g. a search page with search again, back, fwd, begin, end etc.
I think page-driven development frameworks would exacerbate this problem unless they clarify with eloquence up-front how to make a clear seperation of the POST processing from the page preparation required for the next page.
Otherwise the uninitiated are always going to write brittle, hard-to-maintain, hard-to-extend apps.
What I want to see in the future for big apps is a DTD or xml schema that brings JSP code and XHTML mark-up under control. Something that is easily editable by my editor of choice, using syntax-highlighting to show me where my XHTML is up the swanny.
If JSF provides some view components that will output decent table-less XHTML, then I'll jump at it.
Adam
On 11/11/2004 04:55 AM Craig McClanahan wrote: > I'm afraid you'll have to show me that this outcome is likely before > I'll believe any generalizations of this kind of statement. In > particular, what specific anti-patterns do you think developers will > fall prey to? [snip] > ....., it is far from clear to me that the capabilities JSF > does provide are insufficient by themselves for medium-to-large scale > applications -- the definition of "lightweight" is going to be > interesting to identify :-).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
