Skip to Content

Changes for page Java Client-Overview

Last modified by David Avendasora on 2008/07/16 10:13
From version 4.1
edited by David Avendasora
on 2008/01/10 11:03
Change comment: Bringing JC Information up-to-date.
To version 7.1
edited by David Avendasora
on 2008/01/11 21:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,16 @@
1 -Historically there have been three methods of WebObjects Java Client development:
1 +Java Client is a Three-Tier development model for WebObjects. The interface is a Java Application instead of a web page or web service. One of the big advantages of Java Client is that you can easily program client-side logic into the user interface that requires little or no direct communication with the server. This allows for a rich client experience without the complications of Ajax, but now requires extensive Swing programming which has it's own set of hardships.
2 2  
3 +Historically there were three methods of WebObjects Java Client development:
4 +
3 3  1. Direct To Java Client (D2JC)
4 4  1. Java Client using Interface Builder to create NIB files that define the UI
5 5  1. Java Client using Swing
6 6  
7 -The first two types used other files (XML/NIB files) to build the Swing code during run-time. This made for quick development times requiring very little Java code. D2JC was very flexible with the UI controlled almost entirely by text-based configuration files and major changes to the underlying .eomodel file could often-times be reflected in the UI with no refactoring at all.
9 +The first two types used other files (XML/NIB files) to build the Swing code during run-time. This made for quick development times requiring very little Java code. D2JC was very flexible with the UI controlled almost entirely by text-based configuration files (the same rules-system used by Direct to Web) and major changes to the underlying .eomodel file could often-times be reflected in the UI with no refactoring at all.
8 8  
9 -Unfortunately both of these first two methods suffered from poor on-going support and low usage. Both have since been depreciated. NIB-based development has been deprecated due to the deprecation of the tools required for development. D2JC has been deprecated as well, but no external tools are required to build or modify a D2JC application.
11 +Unfortunately both of these first two methods suffered from low usage and therefore little support was available within the community. Both have since been deprecated. NIB-based development was deprecated due to the deprecation of the tools required for development. D2JC has been deprecated as well, even though no external tools were required to build or modify a D2JC application.
10 10  
11 -Building a WebObjects Java Client application using pure Swing has **not** been deprecated and still exists in WO 5.4.
13 +The good news is that building a WebObjects Java Client application "The Third Way" using pure Swing has **not** been deprecated and still exists in WO 5.4.
12 12  
13 13  While there are not a lot of WebObjects Java Client projects when compared to the quantity of Web-Based projects, it seems to be getting more attention now than it has in several years.
14 14