The Document Renderer Client was introduced in Blueriq 14.9. |
Table of contents
The Document Renderer Client Component provides the ability to render PDF documents, using the Document Renderer Service. Documents can be generated by modelling the AQ_Document_Generate, AQ_Document_Renderer, or AQ_DocumentLink.
This component requires the document renderer service to be installed and configured. See configuring the document renderer service to enable it.
In order to use this component, the profile must be active. If the profile is not active, the deprecated embedded document renderer will be used.
More information on how to configure the application using Spring Profiles can be found here : External application configuration with Spring Profiles.
Add the artifact with groupId com.blueriq and artifactId blueriq-component-document-renderer-client as a dependency to your Blueriq runtime POM file if you want to depend on it.
Please note that you need to add the following configuration. There are no default value for these properties, and the project does not run without setting these properties. |
IDocumentImageProvider type. Consult the Javadoc for details about this interface.To create custom renderer create Spring bean implementing IXmlElementRenderer interface with AquimaDocumentXmlRenderer annotation. AquimaDocumentXmlRenderer annotation has a required elementClass parameter which has to be type of class that extends IElement.
By decoupling document rendering from the Runtime into its own service, a performance penalty was introduced. The Runtime will send the document rendering request to the renderer service which contains the document layout and contents including the to be renderer images. This done via a standard HTTP call. We have noticed that the size of the document and the images will influence the overall roundtrip of the rendering request.