2. Exadel
About Me
● Senior Systems Engineer at Exadel
◦ JSF, RichFaces, Java EE
◦ exadel.org – open source projects and
community
◦ Tiggr (http://gotiggr.com) – interactive
Web and mobile HTML prototypes
3. Exadel
4
New!
Author of Lead-author of
Practical RichFaces Practical RichFaces, 2/e
(Apress) (Apress, June 2011)
12. Exadel
Products
● Open Source with JBoss
◦ RichFaces
◦ JBoss Tools/JBoss Developer Studio
● exadel.org
◦ Flamingo
◦ Fiji (JSF – JavaFX/Flex integration)
◦ jsf4birt (JSF – BIRT/Actuate integration)
◦ JavaFX Plug-in for Eclipse
● Tiggr – interactive Web and mobile HTML
prototypes
13. Exadel
Services
● Rich enterprise application
development
● Eclipse development
● Custom rich component development
● Mobile development
● Training
● Most projects are done in Eastern
Europe
15. Exadel
JavaServer Faces™ (JSF) is
the standard component-
based user interface (UI)
framework for the
Java EE (5 & 6) platform
JSF 1.2 Java EE 6
JSF 2 Java EE 6
16. Exadel
JSF 2
● JSF 2 is a major upgrade over JSF 1.x
● Many features, ideas taken from
projects such as Seam and RichFaces,
and others
17. Exadel
JSF 2 new features
● Facelets ● New scopes
● Composite ◦ Flash, View,
components custom
● Implicit ● Configuration
navigation via annotations
● GET ● Bean Validation
support
support
◦ h:link, h:button
● Basic Ajax
● Resource loading
18. Exadel
JSF 2 <f:ajax>
● Very basic Ajax functionality
● Greatly
inspired by RichFaces 3
<a4j:support> tag
● Ajax in JSF in 3 easy steps:
1. Firing an Ajax request
2.Partial view processing
3.Partial view rendering
21. Exadel
Attribute Value
Important
Event on which to fire the
<f:ajax> event
Ajax request
attributes @all
@this (default)
@form
execute
@none
Id's
EL
@all
@this
@form
render
@none (default)
Id's
EL
22. Exadel
That's good, but where do
you get rich components and
more?
A rich component framework
is still(?) needed to build
real-world
Ajax applications.
23. Exadel
RichFaces 4 – rich JSF framework
● JSF 2 based
● Components
◦ a4j:* tag library (core)
◦ rich:* tag library (UI)
● Skins
● Client-side
validation (Bean
Validation/JSR 303 based)
● CDK – Component Development Kit
24. Exadel
RichFaces versions
Version JSF 1.1 JSF 1.2 JSF 2
RichFaces 3.1.x •
RichFaces 3.3.3* • •
RichFaces 4 •
* Note: RichFaces 3.3.3 has basic JSF 2 support
26. Exadel
RichFaces history
2005: started by Alexander Smirnov
2005-2007: Developed by Exadel
Ajax4jsf - open source, free
RichFaces - commercial
2007: JBoss takes over
Exadel team continues to develop
the framework, project is known as
RichFaces
30. Exadel
RichFaces 4
● All components are reviewed for
consistency, usability
● Redesigned following semantic
HTML principles
● Server-side
and client-side
performance optimization
● Strict code clean-up and review
32. Exadel
RichFaces 4
● Newand easy to use CDK
(Component Development Kit)
● Quickly build your own custom rich
components
33. Exadel
Cloud deployment
● Google App Engine (GAE)
● Amazon EC2
● Special Maven-based plug-in
available
34. Exadel
RichFaces <a4j:ajax>
● 100% based on standard <f:ajax>
● Just replace f: with a4j: and get
exactly the same functionality
● But, you get extra features...
<h:commandButton>
<f:ajax execute="@form" render="output"/>
</h:commandButton>
<h:commandButton>
<a4j:ajax execute="@form" render="output"/>
</h:commandButton>
35. Exadel
<a4j:ajax> attributes
Attribute Description
onbegin JavaScript to execute before Ajax request
JavaScript to execute after response
onbeforedomupdate
comes back but before DOM update
oncomplete JavaScript to execute after DOM update
Skips Update Model and Invoke
bypassUpdates Application phases, useful for form
validation
Skips all a4j:outputPanel
limitRender ajaxRender=”true” areas. Only renders
what is set in current render
status Status to display during Ajax request
41. Exadel
<a4j:push>
● Server-side events are pushed to
client using Comet or WebSockets.
● Implemented using Atmosphere
● Providesexcellent integration with
EE containers, and advanced
messaging services
<a4j:push address="topic@chat"
ondataavailable="alert(event.rf.data)" />
42. Exadel
RichFace 4 core – advanced
features and rendering
● a4j:outputPanel
● limitRender attribute
● render=”{bean.renderList}”
● a4j:param
43. Exadel
<a4j:outputPanel> – auto
rendered panel
<h:selectOneMenu value="#{bean.fruit}">
<a4j:ajax listener="#{bean.change}"/>
</<h:selectOneMenu>
<a4j:outputPanel ajaxRendered="true">
<h:panelGrid>
...
</h:panelGrid> Rendered on every
<h:panelGrid> Ajax request
...
</h:panelGrid>
</a4j:outputPanel>
44. Exadel
Advanced rendering options:
limitRender
<a4j:commandButton render="output"/>
<a4j:commandButton render="output" limitRender="true"/>
<h:panelGrid id="output">
Turns off all auto rendered panels,
...
only renders what is set in current
</h:panelGrid> render
<a4j:outputPanel ajaxRendered="true">
...
</a4j:outputPanel>
45. Exadel
render=”#{bean.renderList}”
JSF RichFaces
1) Ajax request sent 1) Ajax request sent
2) Component id's to be 2) Component id's to
rendered resolved be rendered
3) Component id's are resolved
rendered into the page 3) Component id's
4) 2nd Ajax request is sent. are rendered
In this request the
components (resolved in
step 2 are sent with
request) will be rendered
46. Exadel
<a4j:param>
● Similar to <f:param> but simpler as it
also assigns the value to a bean
property automatically
<a4j:commandButton value="Save">
<a4j:param name="product" value="1009"/>
</a4j:commandButton>
public class Bean {
private String product;
public void setProduct (String product) {...}
public String getProduct () {...}
}
53. Exadel
JSF 2 queue
● JSF2 has very basic queue
functionality
● Events are queued and fired one at a
time
● Only one request is processed on the
server at a time
54. Exadel
RichFaces queue upgrades
● Delay firing of a request
● Combine requests from one or more controls
● Cancel DOM updates if “similar” request was
fired
● Define queue as:
◦ Global (all views have queue)
◦ View-based
◦ Form-based
◦ Named (used by particular components only)
58. Exadel
JavaScript interactions
<h:commandLink value="Link"
<f:ajax onevent="ajaxEvent();">
</h:commandLink>
Called three times:
1) begin
2) success
3) complete
<a4j:commandLink value="Link"
onbegin="ajaxOnBegin()"
onbeforedomupdate="ajaxOnBeforeDomUpdate()"
oncomplete="ajaxOnComplete()">
</a4j:commandLink>
Events are separated for easier development
59. Exadel
RichFaces UI components
● Output, panels
● Input
● Menu
● Data iteration
● Tree
● Drag and drop
● Client side validation
● Miscellaneous
75. Exadel
RichFaces client functions
Function Description
rich:client(id) Returns component client id
rich:element(id) Returns DOM element
Returns RichFaces client component
rich:component(id)
instance to call JS API method
rich:isUserInRole(role) Returns if the user has specified role
Returns component instance for given
rich:findComponent(id)
short id
76. Exadel
rich:component(id) function
● Allows to call JS API on a component
<input type="button"
onclick="#{rich:component('popup')}.show();"
value="Open" />
<rich:popupPanel id="popup">
<h:outputLink value="#"
onclick="#{rich:component('popup')}.hide();
return false;">
<h:outputText value="Close"/>
</h:outputLink>
</rich:popupPanel>
82. Exadel
Skins
● Lightweight extension on top of CSS
● Change
look and feel of all rich
component with a few minor changes
● Can
be applied to standard JSF and
HTML tags as well
85. Exadel
Skins
● Modify existing or create your own
<context-param>
<param-name>org.richfaces.skin</param-name>
<param-value>myCoolSkin</param-value>
</context-param>
● Change skins in runtime
<context-param>
<param-name>org.richfaces.skin</param-name>
<param-value>#{bean.skin}</param-value>
</context-param>
86. Exadel
Overwriting skins
<style>
.rf-p-hr {
// your custom style, applied to all panels on
// on page
}
.panelHeader {
// custom header style
}
</style>
<rich:panel id="panel1">
...
</rich:panel id="panel2">
<rich:panel headerClass="panelHeader">
...
</rich:panel>
87. Exadel
Skinning standard JSF tags
and HTML tags
Apply to each control:
<h:button style="background-color:
'#{richSkin.tableBackgroundColor}'"/>
Apply to all standard controls (JSF and HTML):
<context-param>
<param-name>
org.richfaces.enableControlSkinning
</param-name>
<param-value>true</param-value>
</context-param>
88. Exadel
Skinning standard JSF tags
and HTML tags
<context-param>
<param-name>
org.richfaces.enableControlSkinningClasses
</param-name>
<param-value>true</param-value>
</context-param>
<div class="rfs-ctn">
<h:panelGrid columns="1">
Can be applied to
<h:outputText /> <h:panelGrid>, <rich:panel>, <div>
<h:inputText /> Any standard controls inside the
<h:commandButton /> container will be skinned using
</h:panelGrid> standard controls skinning classes.
</div>
89. Exadel
Where can I try the new
RichFaces 4?
http://richfaces-showcase.appspot.com
90. Exadel
How can we help with RichFaces
● Web development
with RichFaces
Training Days
● Version 3 to 4 migration JSF 1.2, 2 1-2
● Performance tune-up RichFaces 3, 4 1-2
JSF and RichFaces 2-3
● Custom component RichFaces 3 to 4 1-2
development
● On-site training