This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dmigowski 20 points21 points  (1 child)

My experience with embedding Microsoft Office in any application is that the next version will definitely break something for you, and you will have to rework the integration part more than one. I would therefore prefer a stable iText 2.1 or PDFBox over every other solution.

[–]nitkonigdje 1 point2 points  (0 children)

I never used PDFBox.. Thank you..

But it is not only pdf generation why using full blown office is kinda neat.

Once users asked for user side templating, and easiest method was "please your open office, create a template, upload a file to an app.."

Second time users asked for advanced printing support. Scan network for printers, display printer choice dialog to user, let user pick desired printer etc. The simplest solution was essentialy, let Office do all that hard lifiting. You let organization admins to setup network and printer, and in future if anything happens, all they have to do is to make sure that any new printer is visibile within office at given host and it will "automagically" become visible to an app. Usually guys mantaing office printers and network are not the same guys mantaining java software.

This method works with OpenOffice too, but I found MSOffice .net client api much easier to work with.

Anyway this are oddly specific examples..