Your SlideShare is downloading. ×



Published on

Published in: Technology, Education
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. JSF 2: миф или панацея? Магический мир пользовательских интерфейсов.Сергей Моренец29 августа 2012 г.
  • 2. Agenda• The history of Java Web frameworks• JSF specification and roadmap• JSF plugins and extensions• Custom components design• Q&A
  • 3. Distributed App UI History
  • 4. Imagination
  • 5. Reality
  • 6. The history of Java Web frameworks
  • 7. The Servlet API• The introduction in March 1998• Enabled Java developers to write server-side code for delivering dynamic Web content• Java response to CGI
  • 8. JavaServer Pages• Released in 1999 by Sun Microsystems• High-level abstraction of Java servlets• Java response to PHP• Adds tags and expression language• Works inside JSP container, which handles all JSP page view requests.
  • 9. Apache Struts• Introduced by Apache Foundation in 2000• Implementation of the Model-View-Controller paradigm• Enabled actions to support navigation• Templates in JSP, XML, Velocity• Struts 2 with AJAX and plugins support
  • 10. Spring MVC• Released under Apache 2.0 license in 2003• Spring response to Struts framework• Tightly coupled to the Spring IOC container• Defines strategy interfaces for the responsibilities• Supports portlet development
  • 11. The Birth of JSF• Created as JSR #127• Designed by Sun, Oracle, IBM and BEA in May 2001• J2EE framework for building Web applications
  • 12. The JSF Design Goals• Create a standard UI component framework• Define a set of lightweight Java classes for UI components, component state, and input events• Provide a set of common UI components• Provide a JavaBeans model for dispatching events from client-side UI controls to server-side application behavior
  • 13. The JSF Design Goals• Define APIs for input validation, including client-side validation• Specify a model for internationalization and localization• Automatic support of all available client configuration data, such as the browser version• Support Web Accessibility Initiative (WAI)
  • 14. History of JSF• Simple things should be simple. Complex things should be possible. Alan Kay
  • 15. JSF 1.0• Initial release in March 2004• Core and performance improvement• Supports Servlet 2.3 and JSP 1.2
  • 16. JSF 1.1• Bugfix release in May 2004• Performance issues• Based on J2EE 1.3
  • 17. JSF 1.2• Release in May 2006• Fully detached from JSP as view technology• Unified expression language support• Lack of Ajax out-of-box support• Core part of J2EE 5
  • 18. JSF 2.0• Release in June 2009• JSP replaced by facelets as view technology• Full Ajax support similar to Ajax4jsf• Annotations and convention-over-configuration invention• New conversation scope
  • 19. JSF Sample Page• <html xmlns=• xmlns:h=• xmlns:f="">• <h:body>• <h:form>• <h2>A Simple JSF Page</h2>• <h:outputText value="#{modelBean.currentDate}">• <f:convertDateTime type="both" timeZone="#{userLocale.timeZone}" />• </h:outputText>• <h:inputText value="#{modelBean.username}"/>• <h:commandButton value="Click Here"/>• </h:form>• </h:body>• </html>
  • 20. ModelBean.javapublic class ModelBean {private Date currentDate;private String username;public Date getCurrentDate() { return currentDate;}public void setCurrentDate(Date currentDate) { this.currentDate = currentDate;}public String getUsername() { return username;}public void setUsername(String username) { this.username = username;}}
  • 21. Configuration file• <?xml version="1.0" encoding="UTF-8"?>• <faces-config xmlns=""• xmlns:xsi=""• xsi:schemaLocation="•"• version="2.0">• <application>• <message-bundle>message</message-bundle>• </application>• <managed-bean>• <managed-bean-name>modelBean</managed- bean-name>• <managed-bean- class>org.mycompany.ModelBean</managed-bean-class>• <managed-bean-scope>session</managed-bean- scope>• </managed-bean>• </faces-config>
  • 22. Component Rendering
  • 23. Component LifeCycle
  • 24. Built on JavaBeans concepts• UIComponent hierarchyPropertiesMethodsEventsValidatorsConvertors• Event modelListener classesEvent objects• Page navigation
  • 25. JSF Implementations• Oracle reference • UI widgets (MyFaces Tomahawk, implementation MyFaces Trinidad, MyFaces• Sub-project of Glassfish Tobago) • Extension packages to (MyFaces Orchestra, MyFaces Extensions Validator, MyFaces Extensions CDI) • Integration modules ( MyFaces Portlet Bridge)
  • 26. Mojarra vs. MyFaces performanceTestcase MyFaces (ms) Mojarra(ms)1. JSF Protocol Tests 239 2072. Full Body 42 35Replacement3. Multi form situation 4134 44264. Testing for 24 34decorated api calls5. Double Eval 2047 2060Detection6. Table Test,replacement of table 7289 9229elements6. Partial Page 2168 2308Rendering Nav Case7. Event Lifecycle test 130 131
  • 27. Ajax-enabled components and frameworks• jBoss RichFaces, Ajax-enabled JSF components for layout, file upload, forms, inputs and many other features.• ICEfaces, open-source, Java JSF extension framework and rich components, Ajax without JavaScript• PrimeFaces Ajax framework with JSF components• Oracle ADF Faces Rich Client, Oracle Application Development Framework• Backbase Enterprise Ajax — JSF Edition, Ajax framework• IBM Lotus Notes - XPages• MyFaces, The Apache Foundation JSF implementation with Ajax components• Sun Java BluePrints AJAX Components• ZK Ajax framework with JSF components
  • 28. RichFaces 4
  • 29. • A full set of AJAX enabled components• Client-side validation• Advanced queuing• Push component upgrades including JavaMessaging Service (JMS) integrations• Component Development Kit (CDK).• Comprehensive documentation covering development best practices, and component details.• Detailed and automated testing facilities for components, actions, listeners, and pages.• Broad cross-browser support
  • 30. RichFaces Components• Ajax4JSF• RichFaces
  • 31. Ajax4JSF• Core Ajax functionality• Page-level Ajax support• Utility components
  • 32. Rich components• Self-contained and advanced UI components• Extension of standard JSF components• Pluggable customization though Ajax support
  • 33. A Historical Perspective• Created as Telamon project in 2005 by Alexander Smirnov• Released in 2006 as part of Exadel Visual Component Platform• Split into open-source Ajax4jsf and commercial RichFaces in 2006• Made open-source in 2007 as Jboss Ajax4jsf and Jboss RichFaces• Merged as single RichFaces product in September 2007
  • 34. Alexander Smirnov• Architect of the Jboss Richfaces project• Java Server Faces expert group member• Jboss GateIn portal developer
  • 35. RichFaces Team
  • 36. Client Side Validation
  • 37. Data Table
  • 38. Popup Panel
  • 39. Data Grid
  • 40. Tree
  • 41. Rich Editor
  • 42. Pick List
  • 43. Push
  • 44. RichFaces Push• Server-side push technique• Based on Atmosphere framework• Client-side support(Comet, HTML5 WebSockets)• Integration with Java Messaging Service
  • 45.• public Date getDate() {• return new Date();• }•• public void push() throws MessageException {• TopicKey topicKey = new TopicKey("sampleAddress");• TopicsContext topicsContext = TopicsContext.lookup();•• topicsContext.publish(topicKey, "empty message");• }
  • 46. Index.html• <a4j:commandButton value="Push!" action="#{richBean.push}" />•• <a4j:push address="sampleAddress">• <a4j:ajax event="dataavailable" render="outputDate" />• </a4j:push>•• <a4j:outputPanel id="outputDate">• Date: #{}• </a4j:outputPanel>
  • 47. Custom components design in JSF 1.2
  • 48.• public class AdvancedDateComponent extends UIComponentBase {• private HtmlSelectOneMenu dayCmb;• private HtmlSelectOneMenu monthCmb;• private HtmlSelectOneMenu yearCmb;• @Override• public String getFamily() {• return "advanced.Date";• }• @Override• public String getRendererType() {• return "renderer.advanced.Date";• }•
  • 49. AdvancedDateComponent.javapublic Object getValue() { ValueExpression _ve = getValueExpression("value"); return (_ve != null) ? _ve.getValue(getFacesContext().getELContext()) : null;}public void setSubmittedValue(FacesContext context) { Map<String, String> requestParameterValuesMap = context.getExternalContext().getRequestParameterMap(); String day = requestParameterValuesMap.get(dayCmb.getClientId(context)); String month =requestParameterValuesMap.get(monthCmb.getClientId(context)); String year = requestParameterValuesMap.get(yearCmb.getClientId(context)); Calendar calendar = Calendar.getInstance(); calendar.set(Integer.valueOf(year), Integer.valueOf(month) - 1, Integer.valueOf(day)); ValueExpression ve = getValueExpression(“value”); ve.setValue(getFacesContext().getELContext(), calendar.getTime());}
  • 50.• public class AdvancedDateRenderer extends Renderer{• @Override• public void encodeBegin(FacesContext context, UIComponent• component) throws IOException {• if(component instanceof AdvancedDateComponent) {• CompositeDateComponent dateComponent = (CompositeDateComponent)component;• dateComponent.refresh();• dateComponent.updateComponents();• }
  • 51.• @Override• public void decode(FacesContext context,• UIComponent component) {• if (component instanceof AdvancedDateComponent) {• AdvancedDateComponent dateComponent = (AdvancedDateComponent) component;• dateComponent.refresh();• dateComponent.setSubmittedValue(context);• }}}
  • 52. Configuration file• <?xml version="1.0" encoding="UTF-8"?>• <faces-config xmlns="">• <component>• <display-name>advancedDate</display-name>• <component-type>advanced.Date</component-type>• <component-class>org.test.component.AdvancedDateComponent• </component-class>• <component-extension>• <renderer-type>renderer.advanced.Date</renderer-type>• </component-extension>• </component>• <render-kit>• <renderer>• <component-family>advanced.Date</component-family>• <renderer-type>renderer.advanced.Date</renderer-type>• <renderer-class>org.test.component.AdvancedDateRenderer</renderer- class>• </renderer>• </render-kit>• </faces-config>
  • 53. Tag configuration file• <?xml version="1.0"?>• <facelet-taglib xmlns="">• <namespace></namespace>• <tag>• <tag-name>advancedDate</tag-name>• <component>• <component- type>advanced.Date</component-type>• <renderer- type>renderer.advanced.Date</renderer-type>• </component>• </tag>• </facelet-taglib>
  • 54. account.xhtml<ui:compositionxmlns="" xmlns:ui= xmlns:h="" xmlns:web=""> <h:outputText value="#{msg[account.birthdate]}" /> <web:compositeDate value=“#{account.birthDate}"/></ui:composition>
  • 55. Custom components design in JSF 2.0
  • 56. Custom components• No configuration, XML or otherwise.• No Java code.• To which developers can attach functionality.• Hot-deploy.
  • 57. compositeDate.xhtml<html xmlns=""xmlns:f=""xmlns:h=""xmlns:cc=""><cc:interface> <cc:attribute name="birthDate" shortDescription="Value of the component" /> <cc:attribute name="days" shortDescription="List of SelectItem objects representing days" /> <cc:attribute name="months" shortDescription="List of SelectItem objects representing months"/> <cc:attribute name="years" shortDescription="List of SelectItem objects representing years" /></cc:interface>
  • 58. compositeDate.xhtml<cc:implementation> <h:panelGrid columns="3"> <h:selectOneMenu value="#{}"> <f:selectItems value="#{days}" /> </h:selectOneMenu> <h:selectOneMenu value="#{date.month}"> <f:selectItems value="#{months}" /> </h:selectOneMenu> <h:selectOneMenu value="#{date.year}"> <f:selectItems value="#{years}" /> </h:selectOneMenu> </h:panelGrid></cc:implementation></html>
  • 59. account.xhtml<ui:compositionxmlns="" xmlns:ui="" xmlns:tr=""> <h:outputText value="#{msg[account.birthdate]}" /> <tr:compositeDate date=“#{account.birthDate}"days="#{days}" months="months" years="#{years}" /></ui:composition>
  • 60. Disadvantages
  • 61. Jobs at
  • 62. StackOverflow tagged questions
  • 63. • High level of understanding• Limited community support• Lack of books and comprehensive documentation• Multiple resource-consuming dependencies• Performance overhead• Migration issues between RF3 and RF4
  • 64. Love bug story• I am migrating from RF 3.3.1 to 4.0. Im experiencing an issue with the tooltip component. Specifying "bottom-left" for the direction attribute results in the following error:• javax.el.ELException: Cannot convert bottom-left of type class java.lang.String to class org.richfaces.component.Positioning• Was this attribute implemented in 4.0? Am I doing something wrong?
  • 65. Love bug story• Just in case someone else has the same issue, Ive figured it out. In RF 4, bottom-right positioning is no longer valid. You have to use bottomRight. I am completely shocked that none of these changes have made it to their online documentation. I have wasted time trying to figure out what was happening with this component. I cannot believe users are expected to go to the API JavaDocs and look through each class for possible attribute values.•• If any RichFaces guys read this, please either update the online documentation or remove it. There are way too many components in there with information that has not been updated and is just plain wrong
  • 66. Q&A• Сергей Моренец,