Parameter Migration: It Is About Time

Since webPDF version 7, a new parameter structure based on JSON and XML schemas has been introduced.

https://docs.webpdf.de/docs/webservices/rest-api/parameters/

This new parameter structure replaces legacy parameters that were previously provided as one combined string connected by &.

Parameter migration​

Legacy parameters:

pdf.embedFonts=true&pdf.archive=true&pdfa.level=3b

New parameters:

<?xml version="1.0" encoding="utf-8"?>

<operation>
    <converter>
        <pdfa>
            <convert />
        </pdfa>
    </converter>
</operation>

Legacy parameters have existed since the first webPDF version and were used via SOAP 1.1 endpoints. Since SOAP 1.1 endpoints are deprecated, parameter migration is required.

https://docs.webpdf.de/docs/webservices/general/soap/

In webPDF versions 7 and 8, legacy parameters are still available for compatibility reasons, but they no longer receive new options. All features added since webPDF 7 are only available in the new parameter structures.

webPDF 8 is the last version that still supports legacy parameters and provides SOAP 1.1 endpoints. When SOAP 1.1 endpoints are deactivated in the next webPDF version, the legacy parameters will also be disabled.

For example, endpoint /webPDF/Converter will no longer be available and must be replaced with /webPDF/soap/converter.

If your webPDF integration has not been migrated yet, now is the right time to do so with webPDF 8.

Update your application now so future webPDF upgrades remain straightforward.

If you need support with parameter migration, contact support@softvision.de. We are happy to help with the migration and answer your questions.