From 2f51405ed5136a2525333061887e7309263674a4 Mon Sep 17 00:00:00 2001
From: Jeremy Grelle
Use of this tag in the head section of a page that contains the Spring Faces components is recommended + as a browser performance optimization in keeping with the + Yahoo performance guidelines. If this tag is not included, the stylesheet includes will be rendered + inline with the first instance of a Spring Faces component that requires them.
]]> + +ResourceServlet.
+
+ The included resource can be either CSS or JavaScript. The type of include to render will be determined
+ from the resource's file extension. The ResourceServlet will set the proper response headers for aggressive
+ caching of the resource by the browser and will gzip the resource if the client browser supports it. These
+ optimizations are in line with the Yahoo performance
+ guidelines. See the javadocs of the ResourceServlet for more information.
resource includes
+ into one HTTP request.
+
+ The child resource components must all be of the same resource type. This is especially
+ useful when combining modularized CSS files for a site. Reducing the number of HTTP requests when a page
+ loads is one of the Yahoo performance guidelines.
inputText component.]]>
+ inputText component.]]>
+ inputText component.]]>
+ inputText component. Field
+ will display a popup calendar when entered.]]>
+ This button will submit the parent form using an Ajax request by default. The component is progressively + enhanced so that the submit will still function with a full page refresh if JavaScript is unavailable on the + client.
+ +The processing of the JSF component tree can be customized through use of the processIds
+ attribute. By default only the button itself will be processed during the postback lifecycle.
The content to render is determined on the server side by using a render action in the flow
+ definition that processes the request. When updating the existing page, the rendered content must be a
+ replacement for an existing identifiable DOM node in the page.
The component is capable of driving transitions to another view with an Ajax request. In that case, a + client-side redirect to the new view will occur so that browser history and normal back button behavior + is still preserved.
]]> +transition element in the flow definition. Setting bind="false"
+ on the transition is equivalent to setting immediate="true"]]>
+ This link will submit the parent form using an Ajax request by default. The component is progressively + enhanced so that the submit will still function with a full page refresh if JavaScript is unavailable on the + client. To achieve this, an HTML button will be rendered initially, and replaced with a JavaScript enhanced + link. The button is rendered with a special "progressiveLink" CSS class so that its look can be customized + as desired.
+ +The processing of the JSF component tree can be customized through use of the processIds
+ attribute. By default only the button itself will be processed during the postback lifecycle.
The content to render is determined on the server side by using a render action in the flow
+ definition that processes the request. When updating the existing page, the rendered content must be a
+ replacement for an existing identifiable DOM node in the page.
The component is capable of driving transitions to another view with an Ajax request. In that case, a + client-side redirect to the new view will occur so that browser history and normal back button behavior + is still preserved.
]]> +transition element in the flow definition. Setting bind="false"
+ on the transition is equivalent to setting immediate="true"]]>
+ The installed JavaScript listener will submit the parent form using an Ajax request. This component is + purely JavaScript based and should only be used in an environment where the availability of JavaScript on + the client is not a concern.
+ +The processing of the JSF component tree can be customized through use of the processIds
+ attribute. By default only the button itself will be processed during the postback lifecycle.
The content to render is determined on the server side by using a render action in the flow
+ definition that processes the request. When updating the existing page, the rendered content must be a
+ replacement for an existing identifiable DOM node in the page.
The component is capable of driving transitions to another view with an Ajax request. In that case, a + client-side redirect to the new view will occur so that browser history and normal back button behavior + is still preserved.
]]> +event="onchange" will fire an Ajax event when the child component's value changes.
+