Hi Kirk, No you simply have to discover the right filters which have to be used ;-)
A more appropriate place to ask is: - dev@api.openoffice.org - http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html But once more if you plan to use this snippet in a multi-threaded environment like your J2EE-Server you need to serialize access in your application or have to have a pool of OO-Instances and dispatch conversion process to one of them. One more thing, I don't think that you need to have OOo/programm-Directory in your class-path OpenOffice 2 libs should locate the soffice.bin itself but I could be mistaken here. Tom Kirk Israel wrote: > Tom, > thanks, that is very cool. > I was able to get the snippet up and running... > Through trial and error I got the correct Jars from my OOo directory I > needed to compile against, > and then Google indicated I needed to include the "OOo/program" directory in > the classpath. > > Was there a "smarter way" I should have know the above? > > And in terms of expanding on that so that it have .doc as input (right now > it seems to only accept .odt) and HTML as output (currently not one of the > options listed in the program), are there any gotchas I should know about or > is it just about finding some appropriate API documentation and doing the > fairly obvious things? > > This was a great first step, many thanks! > -Kirk > > > > > On 4/19/06, Tom Schindl <[EMAIL PROTECTED]> wrote: > >>Hi, >> >>there's a fully functional codesnippet available which does show how >>document-conversion can happen. >> >> >>http://codesnippets.services.openoffice.org/Office/Office.ConvertDocuments.snip >> >>If you are running this from a J2EE application you need to take into >>consideration that ***one*** OO-Instance can not deal with multiple >>request at the same time, so must: >>- serialize access to OO >>- create a pool of instances you connect to and serialize access to them >> >>Tom >> >>Kirk Israel wrote: >> >>>This project got backburnered but is now coming up again, the concept of >>>integrating OOo's doc to HTML conversion as seamlessly as possible into >> >>an >> >>>exisint J2EE application. >>> >>>My understanding is that OOo must be present (copied to, but not >> >>necceaarily >> >>>installed, baed on Mathias' previous comments. At that point, it should >> >>be >> >>>fairly easy to go through with the UNO libraries...is that about the >> >>size of >> >>>it? Am I missing anything, or are there any resources that might make >> >>this >> >>>easier? >>> >>>Thanks, >>>Kirk >>> >> >> >> >> >
