For an immediate request, after transmitting the request to the Arbortext PE server, waiting for a response, and receiving the response, the Client Composer calls the internal method handleResponse. This method examines the response, which will be either an XHTML error message (in case of severe error) or a JAR file containing the result of the publishing operation. handleResponse extracts data from the JAR file and places the files it contains in the locations to which they would have been written had the publishing operation been performed locally. Then handleResponse calls the post-process function in the outer layer of the publishing framework, described in The Outer Layer of the Publishing Framework.

For a queued request, the Client Composer receives a nearly instant response from the Arbortext PE server. The Client Composer immediately returns ok to the inner layer of the publishing framework, which returns to the outer layer, and the operation is finished.

At a later time, the user may launch the Queued Transaction Viewer, which asks the Arbortext PE server for the status of all queued transactions submitted by the user. If a publishing request has completed processing, the user can select the transaction and clicks the Download button. Arbortext Editor retrieves the JAR archive from the Arbortext PE server, then calls the Client Composer’s handleResponse routine, which proceeds as if the JAR file was the response to an immediate request.