Changes for page WOApplication

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.paulh
	1	+XWiki.cmeyer

Content

...	...	@@ -12,7 +12,7 @@
12	12
13	13	|= Property from the wobuild.properties file |= Description |= Default
14	14	| wo.wosystemroot | Usually this is a WebObjects installation directory, like "C:pple". | NEXT//ROOT environment variable, or root directory "/". //
15		-| wo.wolocalroot | Usually this is a "Local" directory under the directory specified by "wo.woroot". | $wo.woroot/Local
	15	+| wo.localroot | Usually this is a "Local" directory under the directory specified by "wo.woroot". | $wo.woroot/Local
16	16	| wo.homeroot | Usually this is a user home directory. | $user.home
17	17
18	18	== Parameters ==
...	...	@@ -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 ==
...	...	@@ -65,39 +65,14 @@
65	65
66	66	The nested ##frameworks## is a [[FrameworkSet>>WOProject-FrameworkSet]] structure that specifies the names of the WebObjects Frameworks that this application is dependant upon. The jar files from these frameworks will be referenced in varios platform-specific depoyment files (such as CLASSPATH.TXT), and specified in the web.xml classpath if an application is deployed as a servlet. When building a FileSet, path should match up to the "**.framework" directory (no need to match individual JAR files).**
67	67
68		-To embed frameworks set embed to true.
69		-
70		-{{note title="Nov13/08 email from Kieran Kelleher" bgColor="#FFFFCE"}}
71		-
72		-Q: _Kieran Kelleher_
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" />}}
75		-
76		-A: _Mike Schrag_
77		-eclipse="true" makes the <frameworks> tag parse your .classpath file to determine framework dependencies.
78		-{{/note}}
79		-
80	80	=== lib ===
81	81
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.
	70	+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.
83	83
84		-To embed jars set embed to true.
85		-
86	86	=== otherclasspath ===
87	87
88		-This nested element is used to add an arbitrary directory or file path to the runtime classpath. For example on Mac OS X, the directory at APPROOT/Resources/SSLKeyStore/ can be added to the runtime classpath by doing something like this:
	74	+? What does this do ?
89	89
90		-{{code}}
91		-
92		-<woapplication>
93		- [...]
94		- <otherclasspath dir="." embed="true">
95		- <include name="Resources/SSLKeyStore" />
96		- </otherclasspath>
97		-</woapplication>
98		-
99		-{{/code}}
100		-
101	101	== Examples ==
102	102
103	103	Create an application "MyApp" with a set of standard frameworks:
...	...	@@ -138,16 +138,3 @@
138	138	</woapplication>
139	139
140	140	{{/noformat}}
141		-
142		-Create an application "MyApp" with embedded frameworks:
143		-
144		-{{noformat}}
145		-
146		-<woapplication name="MyApp" destDir="${dist}/WebObjects/Applications">
147		- ...
148		- <frameworks dir="../Frameworks"embed="true">
149		- <include name="**/*.framework"/>
150		- </frameworks>
151		-</woapplication>
152		-
153		-{{/noformat}}