Skip to Content

Changes for page WOApplication

Last modified by Andrew Lindesay on 2011/07/17 09:52
From version 27.1
edited by Kieran Kelleher
on 2007/10/08 08:08
Change comment: There is no comment for this version
To version 34.1
edited by dlee
on 2007/10/10 21:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.dlee
Content
... ... @@ -25,7 +25,10 @@
25 25  | principalClass | Subclass of WOApplication to use. | Application
26 26  | customInfoPListContent | String to append to the Info.plist. | No
27 27  | stdFrameworks | If set to true, a set of standard frameworks will be associated with the deployed application (default is true). "Standard" frameworks are: JavaWebObjects, JavaWOExtensions, JavaEOAccess, JavaEOControl, JavaFoundation, JavaJDBCAdaptor, JavaXML. | No
28 +| jvm | Path to the JVM binary. Defaults to 'java' | No
28 28  | jvmOptions | String for the JVM options in the classpath. | No
30 +| jdb | Path to the JVM binary. Defaults to 'java' | No
31 +| jdbOptions | String for the jdb options in the classpath. | No
29 29  | webXML | Generate web.xml | No
30 30  | webXML//WOROOT //| Optional parameter for the web.xml | No
31 31  | webXML//LOCALROOT //| Optional parameter for the web.xml | No
... ... @@ -34,9 +34,10 @@
34 34  | webXML//WOtaglib //| Optional parameter for the web.xml | No
35 35  | webXML//CustomContent //| Optional parameter for the web.xml | No
36 36  | version | Version for the Info.plist | No
37 -| frameworksBaseURL | This denotes the directory containing the framework webserver resources bundles (MyFramework.framework, ERExtensions.framework, etc.). This is typically useful for a embedded split install whereby all webserver resource frameworks are embedded in the webserver split install application bundle. The advantage of doing this is of course is clean upgrades with current versions of framework resources being used independently of what is installed on the deployment server. \
38 -The URL is relating to the webserver document root. \
39 -For example: frameworksBaseURL="/WebObjects/${{project.name}}{{/project.name}}.woa/Frameworks" | No
40 +| frameworksBaseURL | This denotes the directory containing the framework webserver resources bundles (MyFramework.framework, ERExtensions.framework, etc.).
41 +\\ This is typically useful for a embedded split install whereby all webserver resource frameworks (all = localroot and systemroot) are embedded in the webserver split install application bundle. The advantage of doing this is of course is clean upgrades with current versions of framework resources being used independently of what is installed on the deployment server.
42 +\\ The URL is relating to the webserver document root.
43 +\\ For example: frameworksBaseURL="/WebObjects/$project.name.woa/Frameworks" | No
40 40  | startupScriptName | ..... | No
41 41  
42 42  == Nested Elements ==
... ... @@ -61,6 +61,10 @@
61 61  
62 62  The nested lib element specifies a [[FileSet>>http://jakarta.apache.org/ant/manual/CoreTypes/fileset.html]]. This should be a fileset of jar libraries required by your application. All files in this fileset will end up in the ##Resources/Java## folder of the application, and will be included on the classpath for this application.
63 63  
68 +=== otherclasspath ===
69 +
70 +? What does this do ?
71 +
64 64  == Examples ==
65 65  
66 66  Create an application "MyApp" with a set of standard frameworks: