Changes for page Java Client-WebStart Distribution Building
Last modified by David Avendasora on 2009/03/30 14:20
From version 27.1
edited by David Avendasora
on 2008/07/17 07:55
on 2008/07/17 07:55
Change comment:
There is no comment for this version
To version 30.1
edited by David Avendasora
on 2008/07/01 16:47
on 2008/07/01 16:47
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Java Client- WebStart DistributionBuilding1 +Java Client-Building - Content
-
... ... @@ -1,4 +1,4 @@ 1 -Your deployed WebStart-distributed application must have a jar of all the client-side classes (and any subclasses of EOGenericRecord that your client-classes extend) in the Project.woa/Contents/WebServerResources/Java/ directory. If you don't include a jar of your client-side classes in this directory, WebObjects silently uses EOGenericRecord instead. This is made obvious by things like default values, client-side validation and other client-side logic not working in the deployed application.1 +Your deployed application must have a jar of all the client-side classes (and any subclasses of EOGenericRecord that your client-classes extend) in the Project.woa/Contents/WebServerResources/Java/ directory. If you don't include a jar of your client-side classes in this directory, WebObjects silently uses EOGenericRecord instead. This is made obvious by things like default values, client-side validation and other client-side logic not working in the deployed application. 2 2 3 3 The following are the instructions when using Ant to build: 4 4 ... ... @@ -30,18 +30,3 @@ 30 30 {{code}} 31 31 <target name="install" depends="setProps,init.install,build.woapp,javaclient,ssdd,war" /> 32 32 {{/code}} 33 - 34 -1. If you are using any Frameworks that have client-side jars then you'll need to copy those jars over to the WebServerResources/Java directory as well. Because I don't want to go modifying any of the woproject files, I just copy the client-side jars of all my Local frameworks (Library/Frameworks/) into my app. Ideally it would only copy over the ones for the frameworks actually in the build path, but this works for now. I'll re-address it after the upcoming classpath changes to be rolled into WOLips. 35 - 36 -{{code}} 37 - 38 -<!-- the Java Client Client-Side Classes --> 39 -<copy todir="${dest.dir}/${project.name}/WEB-INF/${project.name}.woa/Contents/WebServerResources/Java"> 40 - <fileset dir="${wo.wolocalroot}/Library/Frameworks"> 41 - <include name="**/WebServerResources/Java/*.jar"/> 42 - </fileset> 43 - <mapper type="flatten"/> 44 -</copy> 45 - 46 - 47 -{{/code}}