WebWork (Struts Action2)
Just to name a few. Take some time and google all these. Doing so you'll also find many articles and blogs on the differences between them and compared to JSF if you search for things like "Struts vs JSF". Do a little homework. ;)
There's no magic to any of these frameworks.
Originally posted by Jitender Kumar:
I appreciate your effort in listing out the alternatives for JSF and also your effort in spending time to suggest or advice me.
I am actually looking at developing rich web client with UI components embedded into my web application.
Umm, advise what? Do some research of your own into these different frameworks, if you must use a framework, and make an educated choice based on your findings. If you have specific questions about any particular framework, ask them in the appropriate forum. Your question is too broad and oozes with laziness. ;)
Yegor Bugayenko wrote:Take a look at ReXSL, it's a much simplier than JSF and much more testable (when using rexsl-maven-plugin)
Actually, JSF was specifically designed to be testable. It's why the backing beans are POJOs, instead of extensions or implementations of framework-specific classes and interfaces. It's why POJO set/get methods are used to access backing bean data values (properties), and why action methods are simple parameterless POJO method calls. And it's why I spend so much time admonishing people to avoid writing to the framework when a simpler, more portable option is available.
A properly-designed JSF backing bean can be easily tested with bog-standard jUnit, either from Maven/Ant or from within an IDE such as Eclipse, and I do so daily. You don't need the trouble and overhead of setting up a server or mock-server to test, since the beans are POJOS, nor do you need specialized testing plugins.