Just like a composite component you might want to distribute a converter, but how would you package it? Easy, read the rest down below!
Sometimes you need to write a custom converter to converter the client side representation to an object instance and vice versa. What is need to use a custom converter? See below.
When you developed a composite component the namespace you would be seeing would look like "http://java.sun.com/jsf/composite/xxxxxx". But what if you are not allowed to use it that way or you just do not like it, is it possible to change that? Yes it is possible. This blog entry shows you how.
In the previous blog entry we set the stage on how to package a composite component in a JAR. Now we are going to use it!
If you want to share a composite component between projects you should package it in a JAR.
In JSF 2.2 it is has been made easier to work together with a HTML designer. The page below exposes a traditional h:inputText and a h:commandButton using a more HTML 5 friendly way of doing this.
In JSF 2.2 it is possible to define flows, one of the things you would want to do is to be able enter and to exit a flow. This blog entry shows you a sample on how you can enter a flow and also how to exit it properly.
On the #jsf IRC channel Ryan asked how you can get it so the JSF runtime loads resource library contracts from the filesystem. This blog entry will show you how.
In the previous blog entry a single resource library contract was applied. However did you know that you can stack them?
In JSF 2.2 you have the ability to define a resource library contract so you can deliver a different experience on the basis of which user visits your website. This blog entry shows you how you can switch between a resource library contract on the basis of an EL expression.