Skip to Content

Changes for page WOApplication

Last modified by Andrew Lindesay on 2011/07/17 09:52
From version 29.1
edited by Kieran Kelleher
on 2007/10/10 14:36
Change comment: There is no comment for this version
To version 31.1
edited by dlee
on 2007/10/10 21:30
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
... ... @@ -33,7 +33,10 @@
33 33  | webXML//WOAppMode //| Optional parameter for the web.xml | No
34 34  | webXML//WOtaglib //| Optional parameter for the web.xml | No
35 35  | webXML//CustomContent //| Optional parameter for the web.xml | No
36 -| version | Version for the Info.plist | No
39 +| cfBundleVersion | CFBundleVersion for the Info.plist. Default is no version. | No
40 +| cfBundleShortVersion | CFBundleShortVersionString for the Info.plist. Default is no version. | No
41 +| cfBundleID | CFBundleIndetifier for the Info.plist. Defaults to 'com.myapp'. | No
42 +| javaVersion | JavaVersion for the Info.plist. Used for selecting JVM compatibility. Defaults to '1.5+'. | No
37 37  | frameworksBaseURL | This denotes the directory containing the framework webserver resources bundles (MyFramework.framework, ERExtensions.framework, etc.).
38 38  \\ 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.
39 39  \\ The URL is relating to the webserver document root.