|
Joe, Some refactoring will be necessary to take advantage of JSF in Struts applications, however there is a plan in place and that plan is much more likely minimize changes. I agree that custom tags are the weak link of Struts. Their main weakness is that they cannot be used easily in metadata driven applications. Their strength is that they do provide all the support 99% of application developers need and nicely encapsulate display functionality. David Morris >>> joepluta@xxxxxxxxxxxxxxxxx 10/9/2003 1:48:10 PM >>> > From: Buck > > I am out of my league, having only tinkered with Struts, but it seems to > me > that Struts is the JSP equivalent of externally defined workstation files. > It seems to me that writing Struts + JSP by hand is like writing subfile > DDS by hand (no SDA/Code designer.) To me, Struts is more like coding DDS by hand, except that you can use macros that include both the field name and the prompt, and it lays them out for you, but you can only use SOME of the edit codes. It's faster if the supported edit codes work for you, but impossible if they don't. For example, the Tiles tags are now included in Struts. Which is fine, except that Tiles are already deprecated in common usage wuith the coming of the JavaServer Faces spec. There is no clear word as to how the two (Struts and JSF) will co-exist. So, at this time, my feeling is that Struts is still a moving target and that you're trading flexibility for some ease of programming. This is always a poor trade in my book. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.