Microsoft Document to PDF: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==Docx For Java== | ==Docx For Java== | ||
===Maven Central Repository=== | |||
* [https://search.maven.org/search?q=a:docx4j-JAXB-ReferenceImpl Docx4j-JAXB-ReferenceImpl for Docx4j 8 or 11] | |||
* [https://search.maven.org/search?q=a:docx4j-JAXB-Internal Docx4j-JAXB-Internal for Docx4j 8.1.x only] | |||
* [https://search.maven.org/search?q=a:docx4j-JAXB-MOXy Docx4j-JAXB-MOXy for Docx4j 8 or 11] | |||
==Word to Jasper== | ==Word to Jasper== | ||
Revision as of 23:21, 18 January 2021
Docx For Java
Maven Central Repository
- Docx4j-JAXB-ReferenceImpl for Docx4j 8 or 11
- Docx4j-JAXB-Internal for Docx4j 8.1.x only
- Docx4j-JAXB-MOXy for Docx4j 8 or 11
Word to Jasper
Please open the project in Visual Studio Community Edition 2019 then find the following lines from the ReportConversionAddIn\ReportConversionAddIn.csproj. You may comment out or delete following lines and save the file then Visual Studio Community Edition 2019 prompt you to reload the project configuration. Please confirm the reload. After that it will be automatically recreate the ManifestCertificateThumbprint. Hope it will fix your signing issue.
<PropertyGroup>
<SignManifests>true</SignManifests>
</PropertyGroup>
<PropertyGroup>
<ManifestKeyFile>ReportConversionAddIn_TemporaryKey.pfx</ManifestKeyFile>
</PropertyGroup>
<PropertyGroup>
<ManifestCertificateThumbprint>A1FE05DDA1DF10BA23B874A26E7BDF224282D192</ManifestCertificateThumbprint>
</PropertyGroup>