Changes for page Java Client-Overview

Last modified by David Avendasora on 2008/07/16 10:13

From version 14.1
edited by David Avendasora
on 2008/01/14 10:54
Change comment: There is no comment for this version
To version 13.1
edited by David Avendasora
on 2008/01/11 20:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
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.
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 now direct communication with the server. This allows for a rich client experience without the complications of Ajax, but now requires extensive Swing programming.
2 2  
3 3  Historically there were three methods of WebObjects Java Client development:
4 4  
... ... @@ -14,4 +14,6 @@
14 14  
15 15  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.
16 16  
17 -There are a couple third-party developers working on solutions to streamline the development of pure Swing/SWT/etc Java Client applications for Web Objects. See [[Complimentary Frameworks>>JavaClient-Complimentary Frameworks]]
17 +There are a couple third-party developers working on solutions to streamline the development of pure Swing/SWT/etc Java Client applications for Web Objects.
18 +
19 +* Paolo Sommaruga's **JPBinding** [[http://www.jpaso.com/name/XMLBindingForJavaClient]] which is a WebObjects framework that allows building WebObjects Java Client (not D2JC) without the use of Interface Builder and nib files. JPBinding uses a xml file to describe the bindings between the view objects (buttons, tables, text fields, etc) and the model objects (EODisplayGroup, EOAssociation, etc.).