| By Mauro Carniel | Article Rating: |
|
| October 15, 2008 08:45 AM EDT | Reads: |
14,432 |
Before describing solutions available for rich client application development, it would be a good idea to explain what exactly a rich client application is and which rich client topologies can feasibly be built using the Java platform.
In the main, a rich client is a part of a software system that contains a user interface (UI) and whose front end is "rich," i.e., the user interface has rich graphical content and is highly interactive; a rich client application is also called a desktop application, since it provides content and functionalities that are usually provided by applications on the desktop of your own PC (access to local resources, complex user interface, the capability to connect to remote services, etc.).
Enterprise applications are an example of applications that require a "rich" front end, that is, applications employed in enterprises to manage some business process and data, such as CRM and SCM; in that context, having a "rich" front end becomes a determining and critical factor to ensure business productivity.
The term "client" indicates the existence of another layer in the software system, the "server" that usually provides services to the client side. The two layers used together compose a client/server application. A client/server application can usually combine two or three layers, so it is possible to distinguish several rich-client topologies:
• Two-layered client/server applications, where the client side includes both the presentation (user interface) and the business logic (that is, the part of the application that contains data access and manipulation logic); the server side is usually made up of an information system layer, such as a database.
This kind of client is also called a fat client or thick client, because the client could operate independently from other systems, in some cases without depending on a server-side component.
Applications developed using Visual Basic or Delphi are examples of two-layered rich clients. Using the Java platform, it is possible to realize these kinds of applications using, for instance, the Swing toolkit for the user interface and some other technology for database access and manipulation; the latter can be developed using different solutions:
- Using the JDBC directly to access the database
- Using an ORM tool (Object-to-Relational Mapping) or a more simple data mapper tool whose purpose is to abstract the entity-relational model of the database by mapping it to objects and relations between objects
- Using an entity persistence layer, based on JPA, a recent technology based on J2SE 1.5/1.6 having features similar to the ones supplied by an ORM tool
• Three-layered client/server applications, where the client side includes only the presentation (user interface), the server side is focused on the business logic, and the third layer is related to the information system tier, i.e., the database; the server side has the task of providing services to the client side, so it must be accessible from the client side using some kind of communications protocol.
Published October 15, 2008 Reads 14,432
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Mauro Carniel
Mauro Carniel is an architect at Tecnoinformatica Group. He has more than 9 years of enterprise software development experience utilizing J2EE-based technologies, including JSP, JSF, Swing, EJB. He started focusing more on GUI-based client/server Java applications since 1998. He has a MSc in Information Technology from University of Udine, Italy.
![]() |
pettevi 10/30/08 08:31:25 AM EDT | |||
Thanks Mauro, don't forget Flamingo Swing component suite (https://flamingo.dev.java.net) or SwingX (https://swingx.dev.java.net) either. Or the other dozen toolkits out there that don't really raise to the same quality level. |
||||
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Cross-Platform Mobile Website Development – a Tool Comparison
- Three Buzzwords That Every CIO Hears but One They Should Listen To
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Immersing into JavaScript Frameworks
- Workday Reportedly Prepping to Go Public
- Cloud Expo New York: The Java EE 7 Platform - Developing for the Cloud
- Book Review: Sams Teach Yourself Java in 24 Hours
- OpenOffice.com Lives
- Book Excerpt: Introducing HTML5
- Adobe Sends Flex to the Apache Foundation
- Five Years Waiting for JRE 7: Is It Justified? (Part 1)
- Book Excerpt: Java Application Profiling Tips and Tricks
- i-Technology in 2012: Five Industry Predictions
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- OpenXava 4.3: Rapid Java Web Development
- The Next Web Architecture
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Is Write Once Run Anywhere Ever Going to Be a Reality?
- A Cup of AJAX? Nay, Just Regular Java Please
- Java Developer's Journal Exclusive: 2006 "JDJ Editors' Choice" Awards
- JavaServer Faces (JSF) vs Struts
- The i-Technology Right Stuff
- Rich Internet Applications with Adobe Flex 2 and Java
- Java vs C++ "Shootout" Revisited
- Bean-Managed Persistence Using a Proxy List
- Reporting Made Easy with JasperReports and Hibernate
- Creating a Pet Store Application with JavaServer Faces, Spring, and Hibernate
- Why Do 'Cool Kids' Choose Ruby or PHP to Build Websites Instead of Java?
- What's New in Eclipse?
- i-Technology Predictions for 2007: Where's It All Headed?



















