A Spring-Boot micro-service for generating documents (odt, docx, doc, pdf). The service provides 3 end-points :

• '/print/freemarker' which provides generation based on FreeMarker .
• '/print/xdoc' which provides generation based on XDocReport .
• '/print/jasper' which provides generation based on JasperReports Library .

Depending on the selected implementation, you need to provide a compatible template file :

• FreeMarker : any plain text file (txt, csv) with Freemarker placeholders.
• XDocReport : odt, docx, doc document with Freemarker placeholders.
• JasperReport : zip archive containing JRXML files (the main report entry-point MUST be named main.jrxml).

And a data model. Then the merge process will produce a document (odt, docx, doc, pdf, txt, csv) containing the data.

docker pull pcscol/printer-server

printer:
  template:
    base-url: file:///app/resources/templates/xdoc
  freemarker:
    base-path: /app/resources/templates/freemarker
  jasper:
    base-url: file:///app/resources/templates/jasper
    resource-folder: /app/resources/templates/jasper

• printer.template.base-url : base url for xdoc templates
• printer.freemarker.base-path : base path for freemarker templates
• printer.jasper:
  • base-url : base url for jasper templates
  • resource-folder : folder for shared resources (which may be used in templates)

Configure a folder containing your templates resources and configuration :

DATA_FOLDER :

.
├── application.yml
└── templates
    ├── xdoc
        └── certificat.odt
    └── jasper
        └── certificat.zip
    └── freemarker
        └── certificat.csv

docker run -u root -p 8080:8080 -v DATA_FOLDER:/app/resources pcscol/printer-server

The printer-server exposes a swagger UI for testing accessible at: http://localhost:8080/swagger-ui.html?urls.primaryName=v2 You can use it to try the WS :

1. Provide a body

• A FreemarkerPrintMessage if you use the "/print/freemarker" end-point :

{

  // 1 : The name of the template under the 'printer.freemarker.base-path' folder
  "templateName": "certificat.csv"   

  // 2 : The data to merge within the document  
  "data": {"firstName" : "John", "lastName" : "Doe"},

}

• A XdocPrintMessage if you use the "/print/xdoc" end-point :

{
  // 1 : Tell if the generated document must be converted to pdf or just keep the template format  
  "convert": true,

  // 2 : The path of the template. It can be absolute or relative, if so it will be prefixed with the value of $TEMPLATE_BASE_URL. default is 'classpath:/'  
  "templateUrl": "classpath:/certificat.odt"   

  // 3 : The data to merge within the document  
  "data": {"firstName" : "John", "lastName" : "Doe"},

  // 4 : Some metadata about fields : will be detailed below  
  "fieldsMetadata": [
    
  ]
}

• Or a JasperPrintMessage if you use the "/print/jasper" end-point :

{
  // 1 : Tell the type of the exported document : PDF, DOCX, ODT (default is PDF)  
  "exportType": "PDF",

  // 2 : The name of the template (which is also the name of the unzipped folder).  
  "templateUrl": "certificat.zip"   

  // 3 : The data to merge within the document  
  "data": {"firstName" : "John", "lastName" : "Doe"},

  // 4 : map of additional parameters which may be used in the template
  "parameters": {"logo_path" : "path/to/logo.gif", "exporter.all.export.metadataTitle" : "Certificat de scolarité"}
}

2. Set the expected response content type (application/pdf in our case)
3. Click 'Execute'. You should receive a 200 http response, and a link to download the generated document should appear.

NB : In the case where the downloaded file is corrupted use curl instead.

The parameters map may also contain some configuration to apply to the jasper exporter.

• For PDF export see SimplePdfReportConfiguration and SimplePdfExporterConfiguration.
• For DOCX export see SimpleDocxReportConfiguration and SimpleDocxExporterConfiguration.
• For CSV export see SimpleCsvReportConfiguration and SimpleCsvMetadataExporterConfiguration.

The list of all the managed properties is described by the enum JasperExporterConfigParams in the API :

• "exporter.pdf.report.forceSvgShapes"
• "exporter.pdf.report.sizePageToContent"
• "exporter.pdf.report.forceLineBreakPolicy"
• "exporter.pdf.export.allowedPermissionsHint"
• "exporter.pdf.export.deniedPermissionsHint"
• "exporter.pdf.export.metadataCreator"
• "exporter.pdf.export.displayMetadataTitle"
• "exporter.all.export.metadataTitle"
• "exporter.all.export.metadataAuthor"
• "exporter.all.export.metadataSubject"
• "exporter.all.export.metadataKeywords"
• "exporter.docx.export.metadataApplication"
• "exporter.docx.export.embedFonts"
• "exporter.csv.export.writeBom"
• "exporter.csv.export.fieldEnclosure"
• "exporter.csv.export.forceFieldEnclosure"
• "exporter.csv.export.recordDelimiter"
• "exporter.csv.export.fieldDelimiter"

Fields metadata are used to add styling and rendering behaviour to some fields. You can find here some documentation about it :

• Text Styling
• Dynamic image rendering
• List rendering : here and here

The Printer Service expects input templates using the FreeMarker syntax.

L’étudiant ${firstName!"Prénom"} ${lastName!"Nom"} est bien inscrit !

So to exploit the full templating capabilities, you need to learn about FreeMarker !

NB : Sometimes it's not sufficient to just add the marker ${field} in the document text, you need to use a MergeField in Word or a Input-field in OpenOffice.

You can easily generate any type of client for the API by passing the YAML definition to the SwaggerCodegen plugin. The YAML definition is released to mavenCentral under the arfifact : fr.pcscol.printer:printer-api-v2:$VERSION

1. Build the API : ./gradlew :printer-api:build
2. Build the Server : ./gradlew :printer-server:build :printer-server:jibDockerBuild
3. Run the integration test : ./gradlew :integration-test:build