I think JSF and Struts do similar things but in different aspects. Structs tries to improve the MVC in the web side, and JSF is focus on providing standardize way for HTML *creation*. Or as Ko Ko said, it is sth feel like Swing components! Thus, it seems not to take over each other, but is to supplement each other. Am I rite? Nick.
Originally posted by Nicholas Cheung: Or as Ko Ko said, it is sth feel like Swing components! Thus, it seems not to take over each other, but is to supplement each other.
Yeah, Nick, SWING is like client side component and JSF is server side generation of interfaces... It seems that the fame of SWING is fading with its performance... Since once I did follow the SWING's concept and progrmmed it seriously, I am to hear that the role of SWING in window-based application is going down...
Co-author of SCMAD Exam Guide, Author of JMADPlus SCJP1.2, CCNA, SCWCD1.4, SCBCD1.3, SCMAD1.0, SCJA1.0, SCJP6.0
Hi All, JSF is able to completely replace Swing for the most part. Since Struts is so much more mature it obviously will have a deeper and richer feature set but JSF is more or less a complete replacement of Struts. That being said, no one wants to run out and rewrite their whole web app(s) so there are some great integration points between the two. You can continue to use Struts navigation model but use JSF Components. I think both frameworks have a lot of legs so they will both be around for quite some time to come. However since JSF is receiving major investment from just about every major Java vendor involved in web development (app servers, ide makers etc) I think the time will come quickly when JSF will be more feature rich than Struts (but that is just my $0.02 worth).
Hi Dan, on the personal front.. I have 5 kids, yes that is five. I have the amazing blessing of being able to work from home so I don't have the commute problem. It is not all that easy to keep up with the latest and greatest stuff but if you read a lot (JavaRanch, Blogs, etc.) then you will know enough about what is out there to be able to keep your head above water. Then since you are so widely read when a new problem comes up at work you can offer innovative solutions because you know what the rest of the Java community is doing. Always fun being the goto guy However you can't do it all... I don't know much about webservices. I wish I did but I just haven't had time to dig into it. I keep a really big 'stack of stuff' to look at and I try to start with the top thing and dig enough into that I'm satisfied that I know if I currently need it and if I don't need it now I file it in the gray matter for looking into if I do. I went to Colorado Software Summit last year and bloged a ton about it. That trip helped a bunch on getting through that 'stack of stuff'. Mike Clark has a great post on this front... OK enough personal stuff... I think its worth your while to move straight to JSF and keep a passing interest in Struts. However that comes with the caveat that if you must deliver something in the next 6 months you will probably have to go with Struts. I would not build a production system on the current RI (the license might even prevent that). IBM currently has a beta (on the old spec) and I know Oracle and Sun are both working hard to get something out. Give it 6 months and you will have lots of choices. Hope this helps!