Do what you think is interesting, do something that you think is fun and worthwhile, otherwise you won’t do it well anyway.
STUPIDITY is the next level to INTELLIGENCE
The indispensable first step to getting the things you want out of life is this : decide what you want.
The shift of focus will have a profound and enduring effect on the way we write programs.
Ward Cunningham and Ralph Johnson
JSR 339 : VIDEO PRESENTATION
If you know the enemy and know yourself, you need not fear the result of a hundred battles.
If you know yourself but not the enemy, for every victory gained you will also suffer a defeat.
If you know neither the enemy nor yourself, you will succumb in every battle.
Sun Tzu, Chinese general. The Art of War
Ladies and Gentlemen, Like you, I'm intimately convinced that a professional should not promote a bad practice or a bad technology even though it does serve his own interests or those of his company. And that is one reason why, I wrote this blog post as a replacement of my previous one in which I have shown to many of you, how to build a JAX-RS web service with Groovy. But believe it or not, but I did really ask to myself how I did ever think that giving you the knowledge of a scripting language or whatever to write your RESTful web service, could be the key for you to understand how to design a successful RESTful API.
Any intelligent fool can make things bigger, more complex, and more violent
But it takes a touch of genius and a lot of courage to move in the opposite direction.
Ladies and Gentlemen, beyond the fact that I'm going today to share with you, most of the things a developer should know when building a JAX-RS web service with Groovy, this blog post is first and foremost a farewell to the Java language. It was a fun ride but now I think it is high time for me to move on. And how odd and ridiculous is it to build the dynamic parts of my application with a static language?
We build too many walls and not enough bridges.
In my previous blog post, I have asked to many of you this question: "What JSF should become?". And since then, I was quite silent. The reason behind it, is that I was working to build a concrete implementation of this vision and today I'm glad to give you a concrete demonstration of it. So Ladies and Gentlemen, why waiting more? Let's first start with the idea you are expecting in JSF 2.2...
Perfection is achieved through times.
How someone can improve if he has no clear vision of what he could become? I'm asking this tough question to myself while reading to the definition of JSF. As it is written in its specification, JavaServer Faces is a user interface framework designed to significantly ease the burden of writing and maintaining applications that run on a java application server and render their UIs back to a target client. Woow! That is really a lovely definition but is it still relevant in 2011 and beyond? Ladies and Gentlemen, are you sure that we don't need more?
Our standard web framework is built around the greatest design patterns but it definitely lacks the fundamentals. I have read nowhere that JSF has provided any guidance to developers through the form of "development patterns". And we still have the huge pretension to ask you to use a web framework which has no standard development models coming through the form of conventions. Let me now adopt a more professional attitude in order to clarify my position with some concrete examples thus you will better understand what I'm talking about.
For prosperity to be sustained it must be shared.
An experience is relevant only if it can prevent you to repeat the same mistake.
Make it compliant! Yes, Ladies and Gentlemen, Make it compliant! That is my tip of the day and the statement I woke up with today. Like many of you, I have read the Jsf-spec pdf file and as you may know, JSF 2.2 is coming with two major features : Faces Flows and Multi-templating. Did you see that it will be possible to package a Faces Flow and a template as a jar file, or as an exploded directory? And that it will be possible to offer faces flows and templates as re-usable components in a software repository, such as a maven repository ? In other words, the new vision of JSF is “drop in and go”. There is nothing wrong and suspicious in that strategy but I'm only curious to see how this will gonna happen if we haven't any conventions yet. You would be in a big dream if you think that my view can reuse your template if it does not bring well-known areas. Just take a look at this sample to be convinced :