Skip to Content

Changes for page Embedding WOFrameworks

Last modified by Gavin Eadie on 2011/07/29 18:09
From version 55.1
edited by Philippe Rabier
on 2011/07/29 18:09
Change comment: There is no comment for this version
To version 58.1
edited by Philippe Rabier
on 2011/07/29 18:09
Change comment: Migrated to Confluence 4.0

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,10 @@
1 1  == WOLips 3.4.x, and later, Side-note ==
2 2  
3 3  {{warning}}
4 -If you are updating an older project, make sure you get the latest build.xml file. Create a new project, then copy/paste the contents of the fresh build.xml file into your project's build.xml file.
4 +If you are updating an older project, make sure you get the latest build.xml file. Create a new project, then copy/paste the contents of the fresh build.xml file into your project's build.xml file.
5 5  {{/warning}}
6 6  
7 -For WOLips 3.4.x and later, while embedding is built-in, it's not enabled by default. To enable embedding:
7 +For WOLips 3.4.x and later, while embedding is built-in, it's not enabled by default. To enable embedding:
8 8  
9 9  * make sure you are in the WO Explorer view
10 10  * right-click your project folder, select Properties, select WOLips Deployment
... ... @@ -14,28 +14,28 @@
14 14  
15 15  * make sure you are in the Navigator view
16 16  * edit build.properties, and add:
17 -* ##build.app.name=MyApp-2009-07-14##
17 +* {{code language="none"}}build.app.name=MyApp-2009-07-14{{/code}}
18 18  
19 -There is a known bug with WO 5.4.x (for those not using the latest Wonder release) regarding proper linking to your web server resources within the embedded frameworks. The WOFrameworksBaseURL isn't set correctly. To do this you'll need to programmatically set this within your Application constructor:
19 +There is a known bug with WO 5.4.x (for those not using the latest Wonder release) regarding proper linking to your web server resources within the embedded frameworks. The WOFrameworksBaseURL isn't set correctly. To do this you'll need to programmatically set this within your Application constructor:
20 20  
21 -* ##setFrameworksBaseURL("/WebObjects/MyApp-2009-07-14.woa/Frameworks");##
21 +* {{code language="none"}}setFrameworksBaseURL("/WebObjects/MyApp-2009-07-14.woa/Frameworks");{{/code}}
22 22  
23 23  Another way to fix this bug is to set the following launch parameter:
24 24  
25 -DWOFrameworksBaseURL=/WebObjects/MyApp-2009-07-14.woa/Frameworks
25 +-DWOFrameworksBaseURL=/WebObjects/MyApp-2009-07-14.woa/Frameworks
26 26  
27 27  Within build.properties (I may need to be corrected on this), the best approach to linking your embedded framework's web server resources automatically is to include (however the bug noted above breaks this):
28 28  
29 -* ##frameworksBaseURL=/WebObjects/$build.app.name.woa/Frameworks##
29 +* {{code language="none"}}frameworksBaseURL=/WebObjects/${build.app.name}.woa/Frameworks{{/code}}
30 30  
31 31  There was an old bug in the build.xml file but fixed if you have WOLips more recent than october 2010:
32 -[[http://issues.objectstyle.org/jira/browse/WOL-979]]
32 + [[http:~~/~~/issues.objectstyle.org/jira/browse/WOL-979>>url:http://issues.objectstyle.org/jira/browse/WOL-979||shape="rect"]]
33 33  
34 34  == Introduction ==
35 35  
36 -Below is outlined "simple embedding" concepts, however __full embedding__ **and** __split-installing__ are really recommended. This provides fully versioned self-contained bundles of both the application deployment bundle and the webserver deployment bundle. Read the docs on that technique for more **advantages**. This technique fully explained along with a ready-to-use ant build script is available at:
36 +Below is outlined "simple embedding" concepts, however (% style="text-decoration: underline;" %)full embedding(%%) **and** (% style="text-decoration: underline;" %)split-installing(%%) are really recommended. This provides fully versioned self-contained bundles of both the application deployment bundle and the webserver deployment bundle. Read the docs on that technique for more **advantages**. This technique fully explained along with a ready-to-use ant build script is available at:
37 37  
38 -[[Alternative Ant Build Script for Fully Embedded and Split Install Bundles]]
38 +[[doc:Alternative Ant Build Script for Fully Embedded and Split Install Bundles]]
39 39  
40 40  == Simple Approach ==
41 41  
... ... @@ -87,17 +87,31 @@
87 87  
88 88  The various dirs referenced in the build.xml from which you can select the embed option are:
89 89  
90 -|= dir name |= Description
91 -| wo.wolocalroot | /Library/Frameworks/
92 -\\Embedding these is most useful especially if you the codebase for these, like WOnder frameworks or your own, is frequently updated
93 -| user.home | /Library/Frameworks/
94 -| wo.systemroot | /System/Library/Frameworks/
95 -\\This is where Apple's WebObjects frameworks are installed and if your WebObjects version is consistent between your deployment and development platforms, then embedding these is not of much benefit.
90 +|=(((
91 +dir name
92 +)))|=(((
93 +Description
94 +)))
95 +|(((
96 +wo.wolocalroot
97 +)))|(((
98 +/Library/Frameworks/
99 +Embedding these is most useful especially if you the codebase for these, like WOnder frameworks or your own, is frequently updated
100 +)))
101 +|(((
102 +user.home
103 +)))|(((
104 +~~/Library/Frameworks/
105 +)))
106 +|(((
107 +wo.systemroot
108 +)))|(((
109 +/System/Library/Frameworks/
110 +This is where Apple's WebObjects frameworks are installed and if your WebObjects version is consistent between your deployment and development platforms, then embedding these is not of much benefit.
111 +)))
96 96  
97 97  {{note title="Remember to..." bgColor="#FFFFCE"}}
98 -
99 -If you are working with framework source in your Eclipse workspace (which you should be\!), then it is critical that you build and install all frameworks before building the deployment bundles to ensure that the embedded frameworks are the same as the source you have been developing and testing with. See next subsection for one approcah to automating this.
100 -
114 +If you are working with framework source in your Eclipse workspace (which you should be!), then it is critical that you build and install all frameworks before building the deployment bundles to ensure that the embedded frameworks are the same as the source you have been developing and testing with. See next subsection for one approcah to automating this.
101 101  {{/note}}
102 102  
103 103  === Pre-installing Workspace Frameworks Before Embedded Build ===
... ... @@ -134,7 +134,7 @@
134 134  
135 135  ----
136 136  
137 -See also [[FrameworkSet>>WOProject-FrameworkSet]] documentation.
151 +See also [[FrameworkSet>>doc:WOProject-FrameworkSet]] documentation.
138 138  
139 139  Example for embedding WOFrameworks.
140 140  
... ... @@ -142,10 +142,10 @@
142 142  
143 143  Assume two projects: One named Foo( a framework) and the other named Uli (an application). The parent folder has another folder named packandgo.
144 144  
145 -[[image:Folders.png]]
159 +[[image:attach:Folders.png]]
146 146  
147 -The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
148 -1 application target
161 +The [[attach:packageandgobuild.xml]]from the application. Two minor changes to the default build.xml:
162 + 1 application target
149 149  
150 150  {{code}}
151 151  
... ... @@ -167,8 +167,8 @@
167 167  
168 168  {{/code}}
169 169  
170 -The [[^build.xml]] from the packageandgo folder:
184 +The [[attach:build.xml]]from the packageandgo folder:
171 171  
172 172  Just invoke ant in the packageandgo folder and grap the App from the applications folder within the packageandgo folder.
173 173  
174 -[[image:FoldersAfterBuild.png]]
188 +[[image:attach:FoldersAfterBuild.png]]