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
on 2011/07/29 18:09
Change comment:
There is no comment for this version
To version 57.1
edited by Kieran Kelleher
on 2008/09/04 12:55
on 2008/09/04 12:55
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. prabier1 +XWiki.kieran - Content
-
... ... @@ -1,36 +34,3 @@ 1 -== WOLips 3.4.x, and later, Side-note == 2 - 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. 5 -{{/warning}} 6 - 7 -For WOLips 3.4.x and later, while embedding is built-in, it's not enabled by default. To enable embedding: 8 - 9 -* make sure you are in the WO Explorer view 10 -* right-click your project folder, select Properties, select WOLips Deployment 11 -* check the related, if not all, options under Embed Frameworks 12 - 13 -To create a versioned/dated bundle of your app and resources: 14 - 15 -* make sure you are in the Navigator view 16 -* edit build.properties, and add: 17 -* ##build.app.name=MyApp-2009-07-14## 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: 20 - 21 -* ##setFrameworksBaseURL("/WebObjects/MyApp-2009-07-14.woa/Frameworks");## 22 - 23 -Another way to fix this bug is to set the following launch parameter: 24 - 25 -DWOFrameworksBaseURL=/WebObjects/MyApp-2009-07-14.woa/Frameworks 26 - 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 - 29 -* ##frameworksBaseURL=/WebObjects/$build.app.name.woa/Frameworks## 30 - 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]] 33 - 34 34 == Introduction == 35 35 36 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: ... ... @@ -106,7 +106,7 @@ 106 106 107 107 {{code}} 108 108 109 -<!-- Install my own dependent frameworks in final local install location before embedding --> 76 + <!-- Install my own dependent frameworks in final local install location before embedding --> 110 110 <target name="installMyFrameworks"> 111 111 <ant dir="../WKDemography" target="install" inheritall="false" /> 112 112 <ant dir="../WKEmailData" target="install" inheritall="false" /> ... ... @@ -124,7 +124,7 @@ 124 124 125 125 {{code}} 126 126 127 -<target name="build.woapp" depends="installMyFrameworks"> 94 + <target name="build.woapp" depends="installMyFrameworks"> 128 128 129 129 {{/code}} 130 130