DOCSLIB.ORG

Richfaces Developer Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Richfaces Developer Guide RichFaces Developer Guide RichFaces framework with a huge library of rich components and skinnability support RichFaces Developer Guide 1. Introduction ................................................................................................................... 1 2. Technical Requirements ................................................................................................. 3 2.1. Supported Java Versions .................................................................................... 3 2.2. Supported JavaServer Faces Implementations and Frameworks ............................ 3 2.3. Supported Servers .............................................................................................. 3 2.4. Supported Browsers ............................................................................................ 4 3. Getting Started with RichFaces ...................................................................................... 5 3.1. Downloading the RichFaces ................................................................................ 5 3.2. Simple JSF application with RichFaces ................................................................ 5 3.2.1. Adding RichFaces libraries into the project ................................................ 5 3.2.2. Registering RichFaces in web.xml ............................................................. 6 3.2.3. Managed bean ......................................................................................... 8 3.2.4. Registering bean in faces-cofig.xml ........................................................... 8 3.2.5. RichFaces Greeter index.jsp ..................................................................... 9 3.3. Integration of RichFaces into Maven Project ....................................................... 10 3.4. Relevant Resources Links ................................................................................. 16 4. Settings for different environments ................................................................................ 17 4.1. Web Application Descriptor Parameters .............................................................. 17 4.2. Sun JSF RI ...................................................................................................... 20 4.3. Apache MyFaces .............................................................................................. 20 4.4. Facelets Support ............................................................................................... 21 4.5. JBoss Seam Support ........................................................................................ 21 4.6. Portlet Support .................................................................................................. 25 4.7. Sybase EAServer .............................................................................................. 25 4.8. Oracle AS/OC4J ............................................................................................... 25 5. Basic concepts of the RichFaces Framework ................................................................ 27 5.1. Introduction ....................................................................................................... 27 5.2. RichFaces Architecture Overview ....................................................................... 28 5.3. RichFaces Integral Parts ................................................................................... 31 5.4. Limitations and Rules ........................................................................................ 32 5.5. Ajax Request Optimization ................................................................................. 32 5.5.1. Re-Rendering ......................................................................................... 32 5.5.2. Queue and Traffic Flood Protection ......................................................... 35 5.5.3. Queue Principles .................................................................................... 36 5.5.4. Data Processing Options ........................................................................ 41 5.5.5. Action and Navigation ............................................................................. 42 5.5.6. JavaScript Interactions ............................................................................ 42 5.5.7. Iteration components Ajax attributes ........................................................ 44 5.5.8. Other useful attributes ............................................................................ 44 5.6. How To... ......................................................................................................... 45 5.6.1. Send an Ajax request ............................................................................. 45 5.6.2. Decide What to Send ............................................................................. 46 5.6.3. Decide What to Change ......................................................................... 46 5.6.4. Decide what to process .......................................................................... 47 iii RichFaces Developer Guide 5.7. Filter Configuration ............................................................................................ 47 5.8. Scripts and Styles Load Strategy ....................................................................... 49 5.9. Request Errors and Session Expiration Handling ................................................ 51 5.9.1. Request Errors Handling ......................................................................... 51 5.9.2. Session Expired Handling ....................................................................... 51 5.10. Skinnability ..................................................................................................... 52 5.10.1. Why Skinnability ................................................................................... 52 5.10.2. Using Skinnability ................................................................................. 53 5.10.3. Example ............................................................................................... 54 5.10.4. Skin Parameters Tables in RichFaces .................................................... 55 5.10.5. Creating and Using Your Own Skin File ................................................. 56 5.10.6. Built-in Skinnability in RichFaces ........................................................... 57 5.10.7. Changing skin in runtime ...................................................................... 58 5.10.8. Standard Controls Skinning ................................................................... 60 5.10.9. Client-side Script for Extended Skinning Support .................................... 70 5.10.10. XCSS File Format .............................................................................. 71 5.10.11. Plug-n-Skin ......................................................................................... 72 5.11. Definition of Custom Style Classes ................................................................... 79 5.12. State Manager API .......................................................................................... 81 5.13. Identifying User Roles ..................................................................................... 86 6. The RichFaces Components ........................................................................................ 87 6.1. Ajax Support ..................................................................................................... 87 6.1.1. < a4j:ajaxListener > ............................................................................... 87 6.1.2. < a4j:actionparam > .............................................................................. 89 6.1.3. < a4j:form > .......................................................................................... 90 6.1.4. < a4j:region > ....................................................................................... 91 6.1.5. < a4j:support > ..................................................................................... 94 6.1.6. < a4j:commandButton > ......................................................................... 98 6.1.7. < a4j:commandLink > .......................................................................... 101 6.1.8. < a4j:jsFunction > ................................................................................ 102 6.1.9. < a4j:poll > ......................................................................................... 104 6.1.10. < a4j:push > ...................................................................................... 106 6.1.11. < a4j:queue > .................................................................................... 108 6.1.12. < a4j:status > .................................................................................... 112 6.2. Resources/Beans Handling .............................................................................. 114 6.2.1. < a4j:loadBundle > .............................................................................. 114 6.2.2. < a4j:keepAlive > ................................................................................ 118 6.2.3. < a4j:loadScript > ................................................................................ 119 6.2.4. < a4j:loadStyle > ................................................................................. 120 6.3. Ajax Validators ...............................................................................................
Load more

Recommended publications
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • The Snap Framework: a Web Toolkit for Haskell
    The Functional Web The Snap Framework A Web Toolkit for Haskell Gregory Collins • Google Switzerland Doug Beardsley • Karamaan Group askell is an advanced functional pro- the same inputs, always produce the same out- gramming language. The product of more put. This property means that you almost always H than 20 years of research, it enables rapid decompose a Haskell program into smaller con- development of robust, concise, and fast soft- stituent parts that you can test independently. ware. Haskell supports integration with other Haskell’s ecosystem also includes many power- languages and has loads of built-in concurrency, ful testing and code-coverage tools. parallelism primitives, and rich libraries. With Haskell also comes out of the box with a set its state-of-the-art testing tools and an active of easy-to-use primitives for parallel and con- community, Haskell makes it easier to produce current programming and for performance pro- flexible, maintainable, high-quality software. filing and tuning. Applications built with GHC The most popular Haskell implementation is enjoy solid multicore performance and can han- the Glasgow Haskell Compiler (GHC), a high- dle hundreds of thousands of concurrent net- performance optimizing native-code compiler. work connections. We’ve been delighted to find Here, we look at Snap, a Web-development that Haskell really shines for Web programming. framework for Haskell. Snap combines many other Web-development environments’ best fea- What’s Snap? tures: writing Web code in an expressive high- Snap offers programmers a simple, expressive level language, a rapid development cycle, fast Web programming interface at roughly the same performance for native code, and easy deploy- level of abstraction as Java servlets.
    [Show full text]
  • Analysing the Use of Outdated Javascript Libraries on the Web
    Updated in September 2017: Require valid versions for library detection throughout the paper. The vulnerability analysis already did so and remains identical. Modifications in Tables I, III and IV; Figures 4 and 7; Sections III-B, IV-B, IV-C, IV-F and IV-H. Additionally, highlight Ember’s security practices in Section V. Thou Shalt Not Depend on Me: Analysing the Use of Outdated JavaScript Libraries on the Web Tobias Lauinger, Abdelberi Chaabane, Sajjad Arshad, William Robertson, Christo Wilson and Engin Kirda Northeastern University {toby, 3abdou, arshad, wkr, cbw, ek}@ccs.neu.edu Abstract—Web developers routinely rely on third-party Java- scripts or HTML into vulnerable websites via a crafted tag. As Script libraries such as jQuery to enhance the functionality of a result, it is of the utmost importance for websites to manage their sites. However, if not properly maintained, such dependen- library dependencies and, in particular, to update vulnerable cies can create attack vectors allowing a site to be compromised. libraries in a timely fashion. In this paper, we conduct the first comprehensive study of To date, security research has addressed a wide range of client-side JavaScript library usage and the resulting security client-side security issues in websites, including validation [30] implications across the Web. Using data from over 133 k websites, we show that 37 % of them include at least one library with a and XSS ([17], [36]), cross-site request forgery [4], and session known vulnerability; the time lag behind the newest release of fixation [34]. However, the use of vulnerable JavaScript libraries a library is measured in the order of years.
    [Show full text]
  • Cross-Platform Mobile Application for the Cothority
    Cross-Platform Mobile Application for the Cothority Vincent Petri & Cedric Maire School of Computer and Communication Sciences Decentralized and Distributed Systems Lab Semester Project January 2018 Responsible Supervisor Prof. Bryan Ford Linus Gasser EPFL / DeDiS EPFL / DeDiS 2 Acknowledgements We would like to express our special thanks to Linus Gasser who gave us the opportunity to do this very interesting project related to the collec- tive authority (Cothority) framework developed by the DeDiS laboratory at EPFL. We would like to thank him for the valuable help he gave us whenever we needed and for the knowledge he provided to us throughout the semester. Secondly, we would also like to thank our parents and friends who helped us through the hard times of finalising the project within the limited time frame. 3 1 Abstract The Cothority2 framework has been developed and maintained by the DeDiS laboratory at EPFL. This project provides a framework for develop- ing, analysing, and deploying decentralised and distributed cryptographic protocols. A set of servers that runs these protocols and communicates among each other is referred to as a collective authority, or cothority, and the individual servers are called cothority servers or conodes. A cothority that executes decentralised protocols could be used for collective signing, threshold signing, or the generation of public-randomness, to name only a few options. The highest level of abstraction can be created by protocols like the collective signature (CoSi) protocol, the random numbers (Rand- Hound) protocol, or the communication (Messaging) protocol used by the conodes to exchange data. Then come the services, which rely on these pro- tocols.
    [Show full text]
  • The Effect of Ajax on Performance and Usability in Web Environments
    The effect of Ajax on performance and usability in web environments Y.D.C.N. op ’t Roodt, BICT Date of acceptance: August 31st, 2006 One Year Master Course Software Engineering Thesis Supervisor: Dr. Jurgen Vinju Internship Supervisor: Ir. Koen Kam Company or Institute: Hyves (Startphone Limited) Availability: public domain Universiteit van Amsterdam, Hogeschool van Amsterdam, Vrije Universiteit 2 This page intentionally left blank 3 Table of contents 1 Foreword ................................................................................................... 6 2 Motivation ................................................................................................. 7 2.1 Tasks and sources................................................................................ 7 2.2 Research question ............................................................................... 9 3 Research method ..................................................................................... 10 3.1 On implementation........................................................................... 11 4 Background and context of Ajax .............................................................. 12 4.1 Background....................................................................................... 12 4.2 Rich Internet Applications ................................................................ 12 4.3 JavaScript.......................................................................................... 13 4.4 The XMLHttpRequest object..........................................................
    [Show full text]
  • Web Development Frameworks Ruby on Rails VS Google Web Toolkit
    Bachelor thesis Web Development Frameworks Ruby on Rails VS Google Web Toolkit Author: Carlos Gallardo Adrián Extremera Supervisor: Welf Löwe Semester: Spring 2011 Course code: 2DV00E SE-391 82 Kalmar / SE-351 95 Växjö Tel +46 (0)772-28 80 00 [email protected] Lnu.se/dfm Abstract Web programming is getting more and more important every day and as a consequence, many new tools are created in order to help developers design and construct applications quicker, easier and better structured. Apart from different IDEs and Technologies, nowadays Web Frameworks are gaining popularity amongst users since they offer a large range of methods, classes, etc. that allow programmers to create and maintain solid Web systems. This research focuses on two different Web Frameworks: Ruby on Rails and Google Web Toolkit and within this document we will examine some of the most important differences between them during a Web development. Keywords web frameworks, Ruby, Rails, Model-View-Controller, web programming, Java, Google Web Toolkit, web development, code lines i List of Figures Figure 2.1. mraible - History of Web Frameworks....................................................4 Figure 2.2. Java BluePrints - MVC Pattern..............................................................6 Figure 2.3. Libros Web - MVC Architecture.............................................................7 Figure 2.4. Ruby on Rails - Logo.............................................................................8 Figure 2.5. Windaroo Consulting Inc - Ruby on Rails Structure.............................10
    [Show full text]
  • CS 683 Emerging Technologies Fall Semester, 2006 Doc 23 Rails 7 AJAX Nov 16, 2006
    CS 683 Emerging Technologies Fall Semester, 2006 Doc 23 Rails 7 AJAX Nov 16, 2006 Copyright ©, All rights reserved. 2006 SDSU & Roger Whitney, 5500 Campanile Drive, San Diego, CA 92182-7700 USA. OpenContent (http:// www.opencontent.org/opl.shtml) license defines the copyright on this document. References script.aculo.us, Common Ajax Javascript library, http://script.aculo.us/ Surveying open-source AJAX toolkits, Peter Wayner, Inforworld, July 31, 2006, http://www.infoworld.com/article/ 06/07/31/31FEajax_1.html Proprietary AJAX toolkits: The other side of the coin, Peter Wayner, Inforworld, July 31, 2006, http://www.infoworld.com/ infoworld/article/06/07/31/31FEajaxsb_1.html Ajax/DHTML Library Scorecard:How Cross Platform Are They? Musings from Mars ,March 4th, 2006, http:// www.musingsfrommars.org/2006/03/ajax-dhtml-library-scorecard.html Wikipedia, http://en.wikipedia.org/wiki/Main_Page Agile Web Development with Rails 2nd Ed Bl.16 October 25, Thomas & Hanson, The Pragmatic Bookshelf, PDF Rails API, http://api.rubyonrails.org/ Some Ajax Reading Why Ajax Sucks (Most of the Time) Jacob Nielson http://www.usabilityviews.com/ajaxsucks.html Ajax SWik http://swik.net/Ajax Ajax Mistakes How to use XMLHttpRequest Places to use Ajax 2 Web Browsers suck for developing applications HTML is very limited as UI Delay in response from server 3 Reducing Suckiness CSS Javascript XMLHttpRequest 4 Cascading Style Sheets - CSS stylesheet language that describes layout of HTML & XML Provides HTML better control over layout body { background-color: #fff;
    [Show full text]
  • Marian Edu, Acorn IT About Me
    Chatbots & OpenEdge Marian Edu, Acorn IT About me Working with Progress since 1998 4GL & OO, AppServer Architecture & Integration Java, .NET node.js, javascript, typescript angular, nativescript Chatbots & OpenEdge acorn.ro Chatbot A chatbot is a computer program or an artificial intelligence which conducts a conversation via auditory or textual methods. Such programs are often designed to convincingly simulate how a human would behave as a conversational partner, thereby passing the Turing test. Wikipedia Chatbots & OpenEdge acorn.ro Chatbot & AI Natural Processing Language. Semantic vs. Linguistic Model Keyword matching. Don’t really need to pass the Turing test. Chatbots & OpenEdge acorn.ro Usage Virtual Assistants. Messaging Apps. Organisation Apps/Websites. Chatbots & OpenEdge acorn.ro Use Cases Customer Support. e-Commerce. Marketing, news, finance, etc... Chatbots & OpenEdge acorn.ro Skip Theory Assistants Alexa Skills Kit Actions on Google Messaging Integration. OpenEdge Integration. Chatbots & OpenEdge acorn.ro Assistants Understanding User Input NPL, AI, Intents, Workflow IBM Watson Assistant Amazon Alexa Google Assistant Chatbots & OpenEdge acorn.ro Assistants REST Services (PAAS – subscription) JSON payload Intent/Workflow definition (designer) API’s Chatbots & OpenEdge acorn.ro Smart Speakers Speech Recognition Amazon – Echo, Echo dot, Echo Plus, Echo Spot, Echo Auto… Google – Google Home, Mini, Max Facebook – Portal (Alexa) Chatbots & OpenEdge acorn.ro Amazon Alexa Alexa Console – Skills and Intents Fulfilment
    [Show full text]
  • Reactjs Table of Contents
    React #reactjs Table of Contents About 1 Chapter 1: Getting started with React 2 Remarks 2 Versions 2 Examples 3 Installation or Setup 3 Hello World Component 4 Hello World 5 What is ReactJS? 7 Hello World with Stateless Functions 7 For example: 8 Create React App 9 Installation 9 Configuration 9 Alternatives 9 Absolute Basics of Creating Reusable Components 10 Components and Props 10 Chapter 2: Communicate Between Components 12 Examples 12 Communication between Stateless Functional Components 12 Chapter 3: Communication Between Components 15 Remarks 15 Examples 15 Parent to Child Components 15 Child to Parent Components 16 Not-related Components 16 Chapter 4: Components 18 Remarks 18 Examples 18 Basic Component 18 Nesting Components 19 1. Nesting without using children 20 Pros 20 Cons 20 Good if 20 2. Nesting using children 20 Pros 21 Cons 21 Good if 21 3. Nesting using props 21 Pros 22 Cons 22 Good if 22 Creating Components 22 Basic Structure 22 Stateless Functional Components 23 Stateful Components 23 Higher Order Components 24 setState pitfalls 25 Props 27 Component states - Dynamic user-interface 28 Variations of Stateless Functional Components 29 Chapter 5: Forms and User Input 31 Examples 31 Controlled Components 31 Uncontrolled Components 31 Chapter 6: Higher Order Components 33 Introduction 33 Remarks 33 Examples 33 Simple Higher Order Component 33 Higher Order Component that checks for authentication 34 Chapter 7: How and why to use keys in React 36 Introduction 36 Remarks 36 Examples 36 Basic Example 36 Chapter 8: How to setup a basic webpack, react and babel environment 38 Remarks 38 Examples 39 How to build a pipeline for a customized "Hello world" with images.
    [Show full text]
  • Lecture 10 – Ajax and Jquery
    Lecture 10 – Ajax and jQuery INLS 760 Web Databases Spring 2013 Rob Capra AJAX What is AJAX? 1. The “original” Ajax… is in Agamemnon’s army 2. Another Ajax… is “stronger than dirt” 3. Asynchronous JavaScript and XML Where can I get Ajax? 1. Homer’s Iliad 2. Try the grocery store 3. There is nothing to “get” support is built-in to modern browsers. Ajax is a programming technique. 2 What does AJAX do? • Traditional use of HTTP causes pages to be reloaded when data is exchanged • AJAX uses JavaScript’s XMLHttpRequest method to exchange data with the server without reloading the current page. – This enables quick, small transactions – Client can communicate more often with the server – More flexible user-interfaces can be built – Web applications can look/act more like desktop apps 3 Digging Deeper • Traditional HTTP communication – User clicks a link or presses a form button – Client browser makes an HTTP request using either GET or POST – Server processes request and sends a response – Browser loads the response in a new web page 4 Digging Deeper • AJAX – JavaScript event fires • calls user defined JavaScript function – Client browser makes a request using XMLHttpRequest – Client sets a handler to process the response when it arrives • This communication is asynchronous, so response could arrive whenever – When the response arrives, a client handler does something • For example, update just a PART of the page 5 “Real-World” Example • Google Suggest 6 Simple Example – Client Side <form name="myForm"> Name: <input type="text" onkeyup="ajaxFunction();"
    [Show full text]
  • Management Plan 2019
    Ref. Ares(2018)6568914 - 19/12/2018 Management Plan 2019 Directorate-General for European Civil Protection and Humanitarian Aid Operations (DG ECHO) 1 Contents INTRODUCTION: OVERALL OBJECTIVES AND REGULATORY FRAMEWORK ............................. 3 PART 1. MAIN OUTPUTS FOR THE YEAR ........................................................................... 5 PART 2. MAIN ORGANISATIONAL MANAGEMENT OUTPUTS FOR THE YEAR ................................. 24 2 INTRODUCTION: OVERALL OBJECTIVES AND REGULATORY FRAMEWORK The overall context The primary role of the Directorate-General for European Civil Protection and Humanitarian Aid Operations (DG ECHO) of the European Commission is to manage and coordinate the European Union's emergency response to conflicts, natural and technological disasters. It does so both through the delivery of humanitarian aid and through the coordination and facilitation of in-kind assistance, specialist capacities, expertise and intervention teams using the Union Civil Protection Mechanism (UCPM)1. Commissioner Stylianides's mandate is to deliver quick and relevant humanitarian and civil protection assistance to alleviate humanitarian crises around the world, working closely with our Member States, United Nations (UN) partners, NGOs and civil society. As outlined in DG ECHO Strategic Plan 2016-2020, the fulfilment of this mandate directly supports the achievement of three of the Commission's President Juncker ten political priorities: 1) A stronger global actor; 2) Towards a new policy on migration; 3) A new boost for jobs, growth and investment. An underlying principle that ensures the efficient realisation of the three priorities is one of coordination with other Commission services. DG ECHO attaches great importance to the link between humanitarian aid, as a rapid response measure in crisis situations, and more medium and long-term development action.
    [Show full text]
  • Teaching with Feminist Judgments: a Global Conversation
    Scholarly Commons @ UNLV Boyd Law Scholarly Works Faculty Scholarship 2020 Teaching with Feminist Judgments: A Global Conversation Bridget J. Crawford Kathryn M. Stanchi University of Nevada, Las Vegas -- William S. Boyd School of Law Linda L. Berger University of Nevada, Las Vegas -- William S. Boyd School of Law Follow this and additional works at: https://scholars.law.unlv.edu/facpub Part of the Law and Gender Commons, and the Legal Education Commons Recommended Citation Crawford, Bridget J.; Stanchi, Kathryn M.; and Berger, Linda L., "Teaching with Feminist Judgments: A Global Conversation" (2020). Scholarly Works. 1287. https://scholars.law.unlv.edu/facpub/1287 This Article is brought to you by the Scholarly Commons @ UNLV Boyd Law, an institutional repository administered by the Wiener-Rogers Law Library at the William S. Boyd School of Law. For more information, please contact [email protected]. Teaching with Feminist Judgments: A Global Conversation Bridget J. Crawford, Kathryn M. Stanchi, & Linda L. Bergert with Gabrielle Appleby, Susan Frelich Appleton, Ross Astoria, Sharon Cowan, Rosalind Dixon, J. Troy Lavers, Andrea L. McArdle, Elisabeth McDonald, Teri A. McMurtry-Chubb, Vanessa E. Munro, and Pamela A. Wilkinstt Abstract This conversational-style essay is an exchange among fourteen professors-representing thirteen universities across five countries-with experience teaching with feminist judgments. t Bridget J. Crawford is a Professor of Law at the Elisabeth Haub School of Law at Pace University. Kathryn M. Stanchi is the E.L. Cord Foundation Professor of Law at the University of Nevada, Las Vegas, William S. Boyd School of Law. Linda L. Berger is the Family Foundation Professor of Law at the University of Nevada, Las Vegas, William S.
    [Show full text]