-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trying to get RC18 working on Google App Engine #337
Comments
It looks like you have both RC18 and RC12 on your classpath. Remove RC12 and the earlier versions of pdfbox, fontbox and graphics2d. Also be aware of #336 until RC19 is released. |
That is strange... only the ones with the orange tick should be included, but removing them completely from eclipse did give me a different error ... it looks like xmpbox was not needed in rc12 but it is in rc18... does that sound about right? |
So RC18 works on App Engine, but I see the following in the logs... I'm assuming because you can't write to disk in AppEngine. Maybe it would be better (?) to test if its running on app engine org.apache.pdfbox.pdmodel.font.FileSystemFontProvider : Building on-disk font cache, this may take a while (FileSystemFontProvider.java:233) 2019-03-17 12:19:22.199 EDT |
Hi @Rob46, I believe the font cache is built by PDFBOX for rendering PDFs to images (not for generating PDFs). These logs are just saying that since the filesystem didn't provide any fonts, LiberationSans will be used as a fallback for rendering the base fonts. Ideally, PDFBOX wouldn't generate a font cache at all if just used for generating PDFs, but that's an issue for PDFBOX. |
Thanks for the answer. Also, I just wanted to say that the repeating table headers is a GREAT feature... something people have asked me for multiple times. |
I think I've got all the libraries, but I get this exception:
java.lang.NoSuchMethodError: com.openhtmltopdf.pdfboxout.PdfRendererBuilder.useFastMode()Lcom/openhtmltopdf/outputdevice/helper/BaseRendererBuilder;
My code:
libraries:
The text was updated successfully, but these errors were encountered: