Direct packaging
When packaging directly from an image (not through Server Workbench), you must construct a set of packaging instructions specifying which transport, invocation, and URL configurations the image will use.
For example, packaging an HTTP server requires the explicit inclusion of configurations for the 'http' transport, 'http' invocation, and the 'http' URL. This is required as directly packaging an image does not include the loaded code which typically defines these configurations.
SST provides some methods to help you explicitly include the required classes. To use these methods, add a method similar to the following to your application.
packagingRulesFor: aRuleCollector
aRuleCollector image isRunningImage
ifTrue: [
SstUrl addPackagingRulesFor: 'http' to: aRuleCollector.
SstInvocationHandler addPackagingRulesFor: 'http' to: aRuleCollector.
SstTransport addPackagingRulesFor: 'http' to: aRuleCollector.]
This explicit style of packaging ensures that minimal classes are included. While the relevant SST applications (for example, SstHttpSupport) could automatically cause their respective configurations to be included, this may cause these configurations to be unnecessarily included.
The SstPackagingExamples application has example packaging instructions for several SST examples.
Last modified date: 01/29/2015