Skip to Content

Changes for page WOApplication

Last modified by Andrew Lindesay on 2011/07/17 09:52
From version 19.1
edited by pgr
on 2010/01/14 21:04
Change comment: typo
To version 18.1
edited by Paul Hoadley
on 2011/07/17 09:48
Change comment: Updated stale URL.

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pgr
1 +XWiki.paulh
Content
... ... @@ -40,11 +40,11 @@
40 40  | cfBundleShortVersion | CFBundleShortVersionString for the Info.plist. Default is no version. | No
41 41  | cfBundleID | CFBundleIndetifier for the Info.plist. Defaults to 'com.myapp'. | No
42 42  | javaVersion | JVMVersion for the Info.plist. Used for selecting JVM compatibility. Defaults to '1.5+'. | No
43 -| frameworksBaseURL | This denotes the directory containing the framework webserver resources bundles (MyFramework.framework, ERExtensions.framework, etc.).
44 -\\ 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.
45 -\\Defaults to '/WebObjects/Frameworks'.
46 -\\ The URL is relative to the webserver document root.
47 -\\ For example: frameworksBaseURL="/WebObjects/$project.name.woa/Frameworks" | No
43 +| frameworksBaseURL | This denotes the directory containing the framework webserver resources bundles (MyFramework.framework, ERExtensions.framework, etc.).
44 +\\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.
45 +\\Defaults to '/WebObjects/Frameworks'.
46 +\\The URL is relative to the webserver document root.
47 +\\For example: frameworksBaseURL="/WebObjects/$project.name.woa/Frameworks" | No
48 48  | startupScriptName | ..... | No
49 49  
50 50  == Nested Elements ==
... ... @@ -71,7 +71,7 @@
71 71  
72 72  Q: _Kieran Kelleher_
73 73  With regards the woapplication task and nested elements, what does the eclipse="true" attribute of the 'frameworks' nested element do?
74 - {{<frameworks dir="ProjectLocal" embed="$\{embed.ProjectLocal}" eclipse="true" />}}
74 +{{<frameworks dir="ProjectLocal" embed="$\{embed.ProjectLocal}" eclipse="true" />}}
75 75  
76 76  A: _Mike Schrag_
77 77  eclipse="true" makes the <frameworks> tag parse your .classpath file to determine framework dependencies.
... ... @@ -79,7 +79,7 @@
79 79  
80 80  === lib ===
81 81  
82 -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.
82 +The nested lib element specifies a [[FileSet>>http://ant.apache.org/manual/Types/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.
83 83  
84 84  To embed jars set embed to true.
85 85