Skip to Content
Last modified by David Avendasora on 2009/02/05 17:10
From version 47.1
edited by Florijan Stamenkovic
on 2008/06/17 18:51
Change comment: There is no comment for this version
To version 48.1
edited by David Avendasora
on 2008/06/17 14:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Java Client-WebStart Incremental Build
1 +Java Client-Incremental Build
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.flor385
1 +XWiki.avendasora
Content
... ... @@ -1,7 +1,5 @@
1 -There are many ways you can organize and deploy WebObject JavaClient applications. One of the ways to do it is through WebStart. You could manually create a WebStart app, but WebObjects can also do it for you, taking care of JNLP creation, jar organization, and many WebStart nasty bits.
1 +WOLips incremental builder will not automatically create the required jar of your client-side classes and place it in the project.woa/Contents/WebServerResources/Java/ directory as is required by a Java Client application.
2 2  
3 -There is a problem however. The WOLips incremental builder will not automatically create the required jar of your client-side classes and place it in the project.woa/Contents/WebServerResources/Java/ directory as is required by a WebObjects WebStart Java Client application.
4 -
5 5  Without the client classes placed in WebServerResources, Eclipse's built-in Run... command will not work properly as the client application will not have access to its classes and WebObjects will silently fall-back to EOGenericRecord. This causes the confusing condition of the application launching and likely not generating any errors, but not working correctly either.
6 6  
7 7  Below are the steps for adding an additional "Ant Builder" to your project to generate and place the required jar in the right location.