Skip to Content
Last modified by Pascal Robert on 2012/07/21 20:39
From version 23.1
edited by Kieran Kelleher
on 2007/12/10 22:28
Change comment: There is no comment for this version
To version 30.1
edited by Kieran Kelleher
on 2007/12/10 22:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  == Pre-requisites ==
6 6  
7 -This [[script>>^split_embedded_build.xml]] only works with the modern WOLips project format and the WOnderApplication project template format (since the layout of regular. However the script is easily changed to accommodate the "old" standard format by changing the dir names in the script (for example "Sources" in the new project layout was "src" in the old layout)
7 +This script only works with the modern WOLips project format and the WOnderApplication project template format (since the layout of regular. However the script is easily changed to accommodate the "old" standard format by changing the dir names in the script (for example "Sources" in the new project layout was "src" in the old layout)
8 8  
9 9  {{info title="Modern WebObjects Project Layout"}}
10 10  
... ... @@ -18,8 +18,7 @@
18 18  
19 19  Have no fear ;-) , you will not break anything by dropping this script as is into your project and trying it out. You can just use it as is without replacing your default build.xml
20 20  
21 -* So, download the [[script>>^split_embedded_build.xml]] by right-clicking this [[link>>^split_embedded_build.xml]] and selecing Save As... or whatever your browser uses for saving contents at a link destination.
22 -* Drag it to the root of your project.
21 +* So, download the script and drag it to the root of your project.
23 23  
24 24  * Open the Ant run configuration for the script by right-clicking on the script and selecting the menu shown below.
25 25  
... ... @@ -61,27 +61,17 @@
61 61  * Self-contained deployment bundles - all required frameworks are embedded - minimal dependency on target server configuration and versions. For example, there is no need to install Wonder frameworks on your deployment server since the ones you developed and tested with are embedded in the deployment bundles. Experience has shown that this improves consistency of deployment reliability.
62 62  * Compressed gzipped tar archives of both application and webserver bundles are created, ready for copying to target server(s)
63 63  ** This is easily decompressed on the server using
64 -** $ sudo tar xvzf bundle.tar.gz
63 +** $ sudo tar --xvzf bundle.tar.gz--
65 65  
66 66  == Anatomy of Embedded Split Install Bundles produced by this Ant Script ==
67 67  
68 -{{info title="The Deployment Files"}}
69 -
70 -The two compressed "ready-to-deploy" bundles are highlighted below
71 -!build_artifacts.jpg!
72 -
73 -{{/info}}
74 -
75 75  The notable aspects of the embedded build structure are shown below.
76 76  
77 77  === Application Bundle ===
78 78  
79 79  {{info title="Embedded Application Bundle Layout"}}
72 + !app_bundle_layout.jpg!
80 80  
81 -!app_bundle_layout.jpg!
82 -* Opening the app executable (command line script at bundle root having the application name as its name) and looking at the end will reveal that the WOFrameworksBaseURL references the frameworks inside the webserver embedded bundle.
83 -* Examining the Contents/MacOS/MacOSClassPath.txt file will reveal that the java classpath refers to all the jars inside the embedded bundle.
84 -
85 85  {{/info}}
86 86  
87 87  The application bundle typically gets installed as follows: