jcarp03/24/2022, 6:45 PM
bdw429s03/24/2022, 6:47 PM
however I have no idea if it's the same if you used the standard CF installer. I installed the PDf services using the stand alone installer to use with CommandBox, so mine may be in a different location
And it looks like this:
<description> Timeout (in seconds) for PDF conversion task</description>
jcarp03/24/2022, 7:15 PM
Matt Jones03/24/2022, 7:49 PM
Patrick S03/24/2022, 9:05 PM
bdw429s03/24/2022, 9:06 PM
is just a wrapper around the wkthmltopdf library
Patrick S03/24/2022, 9:07 PM
Jonas Eriksson05/23/2022, 12:25 PM
Patrick S05/24/2022, 2:02 PM
bdw429s05/24/2022, 3:59 PM
(I'm kinda lost as to which version people recommend "Classic" or "Flying Saucer".I'm not sure anyone really 'recommends' either. The Flying Saucer is what the newer version of the PDF extension is using. It's more up to date, has more features, and that's the version of the extension receiving fixes. So unless you have old code dependent on some specific behavior of the classic engine, I don't think there's a reason not to be using the new stuff.
the ForgeBox versionCan you be more specific? There's at least 10 packages on Forgebox that appear to be related to "pdf" so I'm not sure which one you're referring to there. https://www.forgebox.io/?search=pdf
I'm just really looking for the simplest and correct way of doing it that is considered "the right modern way"When it comes to generating PDFs, usually whichever way works for you is right 🙂 I'd start with the CFDocument tag and see how well it works for you. It's easy to use and can usually handle average load and average size PDFs pretty good.
Patrick S05/24/2022, 4:01 PM
bdw429s05/24/2022, 4:11 PM
• on Adobe CF is powered by a native Java PDF building library that is proprietary to Adobe
• on Lucee in "Classic" mode is powered by a very old version of a native Java PDF building library called iText
• on Lucee in "Flying Saucer" mode is powered by a recent version of a native Java PDF building library called Flying Saucer, which I think is actually powered by a newer version of iText internally
Now, wkhtmltopdf is a native binary (not java) written in C++ which is compiled for different operating systems. There is a popular Node.js wrapper and when you run the CFHTMLToPDF tag in Adobe ColdFusion, CF is making an HTTP web service call to a Jetty powered java-based API which wraps the actual native Node library to generate the PDF and then send it back.
Most of the Lucee wrappers you see including the lib above is a similar setup, but instead of being a built in CF tag, you just send the API call to a docker container or wherever you've spun up a wrapper for the wkhtmltopdf process. So it's pretty close to what Adobe does, just more manual of a setup.
Jonas Eriksson05/25/2022, 9:26 AM
bdw429s05/25/2022, 2:48 PM
there has been some hick-ups with page margins and font sizes seemingly being affected by various Lucee versions. I know this sounds "muddy" 🙂@Jonas Eriksson No, that's typical experience when it comes to PDFs. Unfortunately, I can't promise that changing to another method of PDf generation will be any different, or even less likely to have little changes between versions. Do put in tickets for any issues you have with cfdocument-- Pothys has done a lot of work to try and get bugs fixed there in Lucee.
sknowlton05/25/2022, 2:53 PM
Patrick S05/25/2022, 2:56 PM