I think Tak's new paradigm of page-driven Struts development will mask this nitty-gritty stuff, and on large or complex apps will lead to these problems - with poor re-use, rigid design of the Command Pattern being locked to the UI, lack of logic in the Command Pattern implementation etc.
But this of course may well be no problem if this paradigm intended for lightweight, quick to deploy apps.
What intrigues me about JSF which I haven't been able to find out yet, is whether JSF is also only meant for light-weight apps. Does JSF's tendency towards page-driven Commands Pattern implementation as Craig mentioned put it in danger of encouraging such Bitter Java anti-patterns?
I also gather that JSF's Controller implementation of the MVC framework is not nearly as robust as the Struts implementation. Would a large application that wanted to use JSF also need Struts?
Adam
On 11/08/2004 11:04 PM Joe Germuska wrote:
Why? It's not like Shale is carved in stone yet. (er... no pun intended). Now is the time for people who are interested in a new version of Struts to talk about it. Craig is putting something out there. He has a clear idea which benefits from a relationship to the JSF apis. A lot of people have hesitated or outright complained (myself included), but no one has yet said much about why JSF is bad. More to the point, critics should either explain how the features Craig delegates to the JSF API could be a delivered in some alternative way, or why those features aren't important enough to merit a tie to JSF.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
