A latest podcast mentions about JSF.
JavaServer Faces (JSF), the great surviver, appears the be late winner of Oracle acquisition of Sun. Oracle continues to prompt JSF technology, as the front end solution for web applications. The new 2.2 specification is ready for HTML5 use more Javascript.
Oracle just has the milestone release for JSF. JSF looks like the crown jewels Oracle looking for from Sun.
Oracle pushes JSF hard. If you choose Oracle, there is no way to escape from JSF.
What's your opinion on JSF? Especially JSF 2.x which is completely revamp of previous JSF 1.x. Facelets instead of JavaServer Pages (JSP) as the display technology. Your comments are welcome.
I'm no longer a developer and I never had the opportunity to really get stuck into Java development. But I attended many a Sun Developer Days conference and other such events where JSF was touted as the next big thing.
From all the code snippets the blokes at Sun showed us, it really did look a whole lot more promising than using JSP. I thought the idea was great, but I also thought that perhaps it was dead.
What & where is the future for Java now anyway? I'm not sure it can survive purely as a "tool" for Oracle products.
It's important don't put your money on a horse can't win. Microsoft, IBM and Oracle is safe trifecta bet if they both in the draw of "Melbourne Cup".
Ruby on Rails is intended to emphasise Convention over Configuration (CoC), and the rapid development principle of Don't Repeat Yourself (DRY).
"Convention over Configuration" means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called Sale by default. It is only if one deviates from this convention, such as calling the table "products sold", that the developer needs to write code regarding these names. Generally, Ruby on Rails conventions lead to less code and less repetition.
"Don't repeat yourself" means that information is located in a single, unambiguous place. For example, using the ActiveRecord module of Rails, the developer does not need to specify database column names in class definitions. Instead, Ruby on Rails can retrieve this information from the database based on the class name.
JSF, on the other hand, borrowed or pitched all these ideas from RoR generously.
If you understand the common sense and principle of computer science, all the new languages, framework, solutions are all come or derive from the same one root ...
I realized it when I started learning Ruby on Rail,I never tough framework in Java and the one in Ruby can be similar.Thanks for your view point