8.0

Alerts
The renderer for this
image type has no way
of rendering the
desired objects.
HTTP Error #406
This alert is displayed when you submit a render request with
the pages or box parameter.
What to do: Do not use the pages or box parameter with a
PPML render type. It does not support these parameters.
This Output Style does
not exist.
This alert is displayed when you specify a non-existent output
style.
This Output Style
cannot be used with
this render type.
This alert is displayed when you specify an output style that
does not conform to the render type.
The file path is invalid.
HTTP Error #500
This alert is displayed when you specify an invalid path with
the path parameter.
Logs
If the project is successfully rendered, a transaction success message is written to the
QuarkXPress Server Transaction Log file. The transaction entry consists of the date
and time of the request, render type, project name, type of response produced by
server, size of response returned in bytes, and client IP address.
The following is a sample of a transaction entry:
8/3/2005 10:03:30 - ppml/sample.qxp - Type: application/postscript - Size:
2654464 - Client: 127.0.0.1
If any alert is displayed, an error message is written to the QuarkXPress Server
Error Log file. The transaction entry in an error log contains the date and time of the
request, the error code, and the error message.
The following is a sample of an error log transaction entry:
8/3/2005 11:27:24 - Error - Error Code: 10008 - The renderer for this image type
has no way of rendering the desired objects.
Example GET
URL
http://localhost:8080/ppml/sample.qxp?paginate=file:MacintoshHD:file.xml
&path=C:\abc&includefont=true
Example, Object
Model
Request Object Name : PPMLRenderRequest
Code Snippet :
//STEP1: Create the QuarkXPress Server Request Context and set the nescessary
properties
sdk.QRequestContext requestCtx = new sdk.QRequestContext();
boolean responseAsURL = false;
requestCtx.setDocumentName(docName);
//STEP 2(SPECIFIC TO REQUESTS):Create the PPML renderer request and
embed it in the request context.
PPMLRenderRequest ppmlreq = new PPMLRenderRequest();
ppmlreq.setExportPath(request.getParameter("path"));
ppmlreq.setLayout(request.getParameter("layout"));
ppmlreq.setOutputStyle(request.getParameter("outputstyle"));
requestCtx.setRequest(ppmlreq);
//STEP3: Create the WIG service and call the processRequest() API
QManagerSDKSvcServiceLocator serviceLocator = new
QManagerSDKSvcServiceLocator();
QManagerSDKSvc service = serviceLocator.getqxpsmsdk();
sdk.QContentData data = service.processRequest(requestCtx);
Please refer to the samples for further details on the use of the WIG object model.
Page 70