Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Warning

This script can be used for WOLips 3.3.x only, the build.xml in WOLips 3.4.x and later already have the split install/embedded stuff built-in.

WOLips 3.4.x, and later, Side-note

Warning

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.

For WOLips 3.4.x and later, while embedding is built-in, it's not enabled by default. To enable embedding:

  • make sure you are in the WO Explorer view
  • right-click your project folder, select Properties, select WOLips Deployment
  • check the related, if not all, options under Embed Frameworks

To create a versioned/dated bundle of your app and resources:

  • make sure you are in the Navigator view
  • edit build.properties, and add:
  • build.app.name=MyApp-2009-07-14

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:

  • setFrameworksBaseURL("/WebObjects/MyApp-2009-07-14.woa/Frameworks");

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):

  • frameworksBaseURL=/WebObjects/${build.app.name}.woa/Frameworks

Introduction

The previous tutorial articles provide details of customization of the default ant build script that is present in your WebObjects projects. This article provides a fully custom build script that you can just drop into your project and use it as an alternative to the default build.xml. This script is called the "split_embedded_build" script. Along with providing the script, this article explains in detail what deployment artifacts are produced by the build. Hopefully the functionality in this script will make their way into the standard script someday with configuration parameters settable in a simple way in the build.properties file.

...