Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>That sentence you quoted is <strong>very generic</strong> and probably said by some people who don't have lot of experience in component based frameworks at all. The aim of a component based framework is to provide you with some pre-built components to avoid having to implement HTML code and its binding to server side by yourself everytime you have a requirement. In case of JSF this is done by a Java Servlet which converts JSF's own code to HTML at server side.</p> <p>That components are by default customizable by specifying some attributes in their declaration, i.e. you can <a href="http://www.jsftoolbox.com/documentation/help/12-TagReference/html/h_selectOneMenu.html" rel="nofollow">look at all the attributes</a> <code>h:selectOneMenu</code> provides to you in order to customize its behaviour. If a component still doesn't meet your requirements at all, you always have the option of implementing your own one.</p> <p>You can also add <strong>JS behaviour</strong> and <strong>CSS styles</strong> to your components, don't forget all the framework does is converting its own tags into plain HTML code which can be understood by the browser. As JS and CSS are applied at client side, you could attach them also to the created components. I think in this case what you're getting confused about is the use of third party component libraries, as <a href="http://www.primefaces.org/showcase/ui/home.jsf" rel="nofollow">Primefaces</a> or <a href="http://showcase5-richfaces.rhcloud.com/" rel="nofollow">Richfaces</a> could be for JSF. This libraries have their own components which also add JS-JQuery behaviour and CSS styles. They'll probably cover most of the cases for your application, but even if you need a more specified solution you always have the choice to do by your own.</p> <p><strong>See also:</strong> <a href="http://docs.oracle.com/javaee/6/tutorial/doc/bnavg.html" rel="nofollow">Creating Custom UI Components and Other Custom Objects</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload