OOoDeamon causes problem for 2 reasons :
- Communicating with Ooo via pipes involves dependencies on JNI libs
- sometimes there seems to be a deadlock on OOoDaemon
After trying to fix, this seems to still be a mess.
The right solution would probably be to remove Ooo Deamon and upgrade to JODConverter 3 that now includes a OOo instnace manager.
=> http://code.google.com/p/jodconverter/wiki/WhatsNewInVersion3
But this would require some more testing :
- JODConv 3 is still in beta
- last quick integration ended up with OOo Daemon
=> For now we can simply add a helper that starts OpenOffice via command line if needed
==> no pooling management
- is required by
-
NXP-5190 Fix ERROR "OOo Daemon thread existed"
- Closed