Thank you, I'll keep it in mind, although the tools didn't look like open source libs. I worked with iText on several projects, years apart, and I have to say, this time around the only issues we had was figuring out where to keep the lib for groovy projects. Locally I store it in Groovy/lib folder and all calls work like magic, but once we moved my code out to Amazon server, we a had hard time deciding where to keep them - the jar iText file. Import statements for "import com.lowagie...." were failing, someone else figured out that "import com.itext...." or something like "import com.pdfitext...." would work instead. So we took that direction for import calls, then the only lib that didn't compile was the Font lib, not sure why, but the simplest thing at that point was to get rid of the references to that particular lib. Very strange, but I'd still recommend iText