Originally posted by Darrin Smith:
I checked the sourcebeat site out looking for the chapter summaries but there seems to be a problem with the server, so I will ask you this question...
Given the Java Server Faces SEEMS to be something that Sun will put emphasis on moving forward, is there anything in your book about integrating Spring with JSF?
Chapter 11 will show you how to integrate Spring with WebWork, JSF and Tapestry. I already have the code written, I just need to package it up and write the chapter. The chapter will likely have some bits and pieces from my upcoming comparing web frameworks
talk at ApacheCon.
BTW, my experience with JSF
was not a good one. I certainly don't hate it
though. In fact, I just joined the JSF Expert Group yesterday so hopefully I can help to make it better and easier to use.
You can read my "I don't hate JSF
" post for information on integrating the two.
BTW, I've read J2EE Design and Development by Rod Johnson which is what got me interested in Spring. I've only done some samples so far, and to me (without your book of course) it was a LOT more complicated to use than Struts. Maybe your book will shed some light on it where as Rod's book really wasn't a Spring "How To".[/QB]
IMO, Spring just seems
more complicated to a lot of people because they're already familiar with Struts.
In reality, if you're comfortable with a web framework, why would you switch. IMO, the best web framework is really an individual choice, not a company or industry choice? If you're more efficient and faster developing with one - I'd stick with it. A Spring-managed middle-tier and backend should be easy to integrate into any java web framework.
I recently started a project using AppFuse
, which has support for using Struts, Spring MVC or WebWork. I chose Struts because I'm not only fastest with it, but because it's tag library is one of the best. Spring requires you to write a lot more HTML/JSP than the others and WebWork has immature client-side validation. The good news is there are JSP
2.0 tag files for Spring, but this project requires we deploy on a 2.3 container.