Java201.com

• Using IBM Rational Software Architect to develop Ajax-supported JavaServer Faces components by Mike Starkey, Guang Qing Zhong, Li Chen, Chuan Yang, Elaine Zhan, Larry Zou   - [Clicks: 10]
  This article explains how to use IBM Rational Software Architect v7.0 to develop Ajax-supported JSF components.
  [Includes sample code]
  http://www.ibm.com/developerworks/rational/library/08/0708_starkey/index.html - Aug, 2008
• An introduction to RichFaces by Joe Sam Shirah   - [Clicks: 76]
  Today's clients want and have begun to expect desktop features in browser-based applications. RichFaces is one of a new breed of user interface component suites available for Java Server Faces (JSF). Among other benefits, RichFaces provides built-in JavaScript and Ajax capabilities to meet those expectations. Joe Sam Shirah adds some new tools to your kit based on experiences with a recent field project, including general setup for using RichFaces with Facelets, and several specific component examples.
  [Includes sample code]
  http://www.ibm.com/developerworks/java/library/j-richfaces/index.html - Mar, 2008
• ICEFaces and Spring 2.5 in Java EE by Henry Roswell   - [Clicks: 57]
  This article explains how to deploy ICEFaces in a Java EE environment, including the ability to push content to multiple sessions as data is updated – even if you’re using Spring to manage JSF backing data.
  http://www.theserverside.com/tt/knowledgecenter-is/knowledgecenter-is.tss?l=ICEFacesandSpringJavaEE - Feb, 2008

[Top]

• Java BluePrints AJAX Components   - [Clicks: 214]
  Asynchronous JavaScript with XML(AJAX) is emerging as a hot technology. The Java BluePrints is helping by providing an early access set of AJAX components for Java EE. These components are built using JavaServer Faces technology.
  https://blueprints.dev.java.net/ajaxcomponents.html

[Top]

• Ajax4jsf   - [Clicks: 265]
  Ajax4jsf is an open source extension to the JavaServer Faces standard that adds AJAX capability to JSF applications without requiring the writing of any JavaScript.
  https://ajax4jsf.dev.java.net/
• G4jsf CDK: GWT-JSF Integration Library Component Development Kit   - [Clicks: 136]
  G4jsf is new open source subproject under Ajax4jsf. The subproject's purpose is to maintain an integration library for the Google Widget Toolkit (GWT) and JavaServer Faces (JSF) that wraps Google widgets into JSF components to fully leverage both technologies. G4jsf CDK is a component development kit for making these components.
  https://ajax4jsf.dev.java.net/nonav/ajax/gwt/gwt-cdk.html
• jMaki Charting   - [Clicks: 58]
  jMaki Charting is a BSD based open source project focusing on providing jMaki enabled widgets for charting. jMaki Charting is built on top of the Dojo Tookit charting APIs.
  https://jmaki-charting.dev.java.net/
• JSF Extensions   - [Clicks: 112]
  This project hosts development of software that extends the capability of the JavaServer Faces specification, including revolutionary, world class, support for using AJAX and JSF. Software within this project is intended to run on any JSF compliant implementation, but in some cases the capabilities are enhanced when run with Sun's implementation.
  https://jsf-extensions.dev.java.net/nonav/mvn/
• Project jMaki   - [Clicks: 63]
  jMaki is all about enabling Java developers to use JavaScript in their Java based applications as either a JSP tag library or a JSF component. jMaki uses the best parts of Java and the best parts of JavaScript to deliver a rich AJAX style widgets.
  [jMaki currently provides bootstrap widgets for many components from Dojo, Script.aculo.us, Yahoo UI Widgets, Spry, DHTML Goodies, and Google. jMaki provides a common interfaces to these widget libraries and allows you to use these libraries together in th]
  https://ajax.dev.java.net/
• weblets by John Fallows, Jonas Jacobi   - [Clicks: 51]
  Component libraries for web application frameworks often need to provide resource files along with implementation classes. For example, JavaServer Faces Renderers often need JavaScript, CSS and image resources. Although dropping in an implementation JAR does make these components libraries available, the resource files must be extracted into the web application root. This can easily lead to inconsistency problems between implementation code and resource files. Weblets aims to solve this problem, without placing undue burden on the application developer. Although JavaServer Faces is mentioned as an explicit example, Weblets aims to solve the general problem in a non-Faces-specific way, and then provide an integration with Faces.
  https://weblets.dev.java.net/

[Top]