Thursday, March 16th, 2006

JSP Controls Tag Library 0.5 Released

Category: Java, JavaScript, Library

JSP Controls Tag Library (the “Library”) allows building dual-mode JSP
components that work in both Ajax and standard mode off the same
codebase. The portlet-like components handle input and render output
in decentralized manner, therefore a central controller or other
coordinator like a portal engine is not required.

The Library utilizes two request processing concepts:

  • Redirect-After-Post for synchronous HTTP request/response cycle
    (non-Ajax mode), and
  • In-place update for asynchronous request/response cycle (Ajax mode).

JSP components take advantage of Ajax mode whenever possible. If
Javascript or XMLHTTPRequest object is not supported, the components
fall back to standard synchronous mode, with no visible degradation of
user expereince. Switching Javascript on and off is possible during

Pages composed with the Library look and behave the same way whether
they run in Ajax mode or in traditional synchronous mode. In fact, a
browser that renders web page in an off-screen buffer, may deliver the
same flicker-free experience in non-Ajax mode as other browsers do in
Ajax mode.

System Requirements

  • Java SDK 1.4.2+
  • Servlet container, supporting servlet specification 2.3+ and JSP
    specification 1.2+ (for example, Tomcat 4)
  • Browser supporting either bare HTTP 1.1 (for standard mode) or
    Javascript + XMLHTTPRequest (for Ajax mode).

Project page:
Live demos:

JSP Controls Lifecycle

Posted by Dion Almaer at 8:03 am

3 rating from 24 votes


Comments feed TrackBack URI

How does the GUI Controls compare with the GUI Classes defined below?

Any comparison of pros and cons?
Where can I find a method to include custom application specific extensions and components?

Comment by anon — March 16, 2006

JSP Controls Tag Library is not intended for what is called “cinematic” experience. Its goal is to provide simple programming model for developing portlet-like components, a.k.a. page fragments. The programming approach used in the library does not require Portal server, all that is needed is JSP1.2 engine. Prior JSP knowledge and JSP taglibs remain fully applicable.

User data is submitted directly to componenents, without passing through central controller like portal engine. A component renders only itself, the library takes care about specifics of composite page update. Asynchronous update of page fragment is used whenever possible, otherwise a whole page is reloaded. Still use Netscape4? No problem.

Originally the library worked in synchronous mode with full page reload. Adding asynchronous in-place update was a natural fit and a valuable enhancement. It allowed to increase application responsiveness, lower network traffic and improve user experience.

When the 1.0 release comes out, it will also contain partial submit feature that will allow to add “suggest”-type behavior to any HTML form.

Comment by Michael Jouravlev — March 16, 2006

[…] And if the above is geek to you, try this ‘Ajax’ overview at the Ajaxian blog […]

Pingback by » Blog Archive » Defacto javascript library roundup — March 18, 2006

Leave a comment

You must be logged in to post a comment.