JSF and Shale appear, in some ways, to be competing technologies and in others to be complementary. When looking to migrate to JSF from Struts at the application layer (retaining a Spring model layer) what (if anything) is to be gained by throwing Shale into the mix with JSF?
Would people generally recommend considering Shale with JSF or would this be a waste of time and effort compared to basing the application layer purely on JSF (with a few Ajax bells and whistles further to the client end)?
We actually provide coverage of Shale at the end of the book. The book takes an agnostic approach to Shale. Basically since every Shale app is a JSF application, you're not really venturing off the path with Faces when working with Shale. Developers needn't worry about getting completely isolated if they use Shale.
That being said, Shale is an interesting technology to watch and see how it evolves.
Joined: Sep 09, 2004
It seems that, at a simplistic level, Shale is a framework within which you can write JSF applications (please correct me if this impression is wrong). Is there much to be gained, in your opinion, from using such a framework with JSF (if we already have a Spring model layer) or might we be better of trying to integrate JSF directly with Spring and forget the learning and application maintenance overhead of introducing Shale in addition to Spring and JSF?
I am very exciting to have this book, because, according to Chris, the book "actually provides coverage of" most asked topics on this forum
Speaking, about Shale, It is really surprised for me that Shale is named as a competing technology to JSF. Shale is based on JSF and cannot live without it. I do not what to speak a lot about the political (hidden) aspect of Shale (killing the popularity of Struts), because it is attained already. Technically speaking, Shale is an extensions to JSF that offers the additions, JSF misses. JSF misses them because at the moment the JSF was been formed the new tendencies in the Web Development (co-called Web2.0) did not exist. It will miss the next ones (like Web3.0, probably) because the lifecycle of new JSF implementation is too long to be actual the the next version is released. So, Shale (or the idea it shows) has a very important mission - it makes JSF actual (modern) right now. Is the Shale is popular itself? We include the Shale support at the beginning of this year. So far, just a few questions. Instead of Facelets, for example. Shale looks like a warehouse on the road. It takes the ideas from other frameworks to show that JSF can do the same, and then the others just polish those ideas to make them practically used. Probably, something will be changed in the future. I only say what I see now.