Changes for page Java Client and Direct To Java Client Example Project using WebStart

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -25,9 +25,7 @@
25	25
26	26	{{/code}}
27	27
28		-1. Create a WOComponent named "JavaClient".
29		-[[image:Picture 11.png]][[image:Picture 10.png]]
30		-This WOComponent will be what passes the specifics about your client-side application to WebObjects.
	28	+1. Create a WOComponent named "JavaClient". This WOComponent will be what passes the specifics about your client-side application to WebObjects.
31	31	1. Modify the JavaClient.html replacing the contents with:
32	32
33	33	{{code title="JavaClient.html Contents"}}
...	...	@@ -50,8 +50,9 @@
50	50
51	51	{{note title="Note!"}}If you are not creating a Direct To Java Client (D2JC) application, then you will need to replace the applicationClassName parameter (com.webobjects.eogeneration.EODynamicApplication) with the name of your client-side application class. Your non-D2JC client-side Application class *must* subclass EOApplication.{{/note}}
52	52
53		-1. If you didn't add an EOModel file to the project when you created it, do it now. Drop any existing EOModel in the Resources directory, or create one from scratch.
54	54	1. Add the following frameworks to the project build path:
	52	+
	53	+{{code}}
55	55	JavaDirectToWeb
56	56	JavaDTWGeneration
57	57	JavaEOApplication
...	...	@@ -66,13 +66,10 @@
66	66	JavaJDBCAdaptor
67	67	JavaWebObjects
68	68	JavaWOExtensions
	68	+{{/code}}
69	69
70		-{{note title="Note!"}}
71		- If you are not creating a D2JC application, then you won't need all of these, but they won't hurt anything either.
72		-{{/note}}
	70	+1. Create a ClasspathClient.txt file in the root of the project and paste the following as contents:
73	73
74		-1. Create a ClasspathClient.txt file in the root of the project and paste the following as contents:{{note title="Note!"}}If you changed the applicaton name in Step 2 above, make sure you change the name of the Client-Side .jar file in the first classpath line below (WebStartJNLPTest.jar). Also be sure to match the case of the project. Client-Side .jar filenames are CamelCase instead of all lowercase as server-side .jar filenames are.{{/note}}
75		-
76	76	{{code title="ClasspathClient.txt File"}}
77	77
78	78	# ApplicationClass == com.webobjects.eoapplication.client.EOClientApplicationSupport
...	...	@@ -163,14 +163,8 @@
163	163
164	164	{{/code}}
165	165
166		-This file is needed to make up for the lack of Java Client application building by the WOLips Incremental Builder. Please follow the [[instructions>>Java Client-WebStart Incremental Build]] for how to create the Java Client Incremental Builder.
167		-
168		-1. If you did not setup the Java Client Incremental Builder, then right-click on the javaclientbuild.xml file and select "Run As -> Ant Build"
169		-[[image:Picture 12.png]]
	162	+1. Right-click on the javaclientbuild.xml file and select "Run As -> Ant Build"
170	170	1. Right-click on the project and select "Run As -> WebObjects Application"
171		-[[image:Picture 13.png]]
172	172	1. Select your.app.Application as the Application class
173		-[[image:Picture 14.png]]
174		-This is it. WebStart should automatically download your client application and launch it. If you are creating a D2JC application and did not put an EOModel file in the Resources directory of your project, then you'll see something like this:
175		-[[image:Picture 15.png]]
176		-If you don't want a D2JC application, then you are on your own for creating the user interface for it. Your client-side application can be a command-line or GUI application. If you want a Swing GUI, then I **highly** recommend Florijan Stamenkovic's [[JBND Framework>>http://web.mac.com/flor385/JBND/]]
	165	+1. Copy the Direct Connect URL from the Eclipse console and paste it into your browser. You should get a "click here" link.
	166	+1. Click it.