Server Composition Extension Processing
Most Server Composition Extensions follow the same basic flow of operation. However, the processing of each Server Composition Extension will depend on the publishing type.
1. The extension creates a content pipeline for the publishing type.
2. Then it copies the content pipeline's default parameters into a Java map.
3. The Server Composition Extension copies the parameters sent by the client into the same map, so that parameters from the client override the defaults.
4. Next, the Server Composition Extension opens the document to be published and calls the appropriate compose_for_type function to invoke the publishing framework. Since the set peservices setting is always off on the Arbortext PE server, the publishing framework will perform the publishing operation.
5. Once the publishing framework returns, the Server Composition Extension closes the document and returns.