5 replies [Last post]
Wed, 2009-12-23 06:14
rustyspoone
Offline
Joined: 2010-06-23

I am running the demos on Mac OS X Snow Leopard. Docmosis looks like a good product. However, I am getting an error whenever I try to execute the runConverter.sh script.

Here is the output. Has anybody seen this before or know what is going on?

machine$ ./runConverter.sh 2100
server port 2100
Starting converter on port 2100
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.LogManager note
INFO: Log4J not found in class path. Using Java logging.
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
INFO: Docmosis version [2.1.0_2867] initialising at Remote Terminus
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
INFO: Please wait...
process err> dyld: Library not loaded: /usr/lib/libxml2.2.dylib
process err> Referenced from: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
process err> Reason: Incompatible library version: DictionaryServices requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
SEVERE: Converter terminating:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.docmosis.document.converter.RemoteConverterTerminus.getConverterService(line:294)
at com.docmosis.document.converter.RemoteConverterTerminus.initConverter(line:283)
at com.docmosis.document.converter.RemoteConverterTerminus.initialize(line:75)
at com.docmosis.document.converter.RemoteConverterTerminus.(line:63)
at com.docmosis.document.converter.RemoteConverterTerminus.main(line:368)
Caused by: java.lang.UnsatisfiedLinkError: com.sun.star.lib.connections.pipe.PipeConnection.createJNI(Ljava/lang/String;)I
at com.sun.star.lib.connections.pipe.PipeConnection.createJNI(Native Method)
at com.sun.star.lib.connections.pipe.PipeConnection.(PipeConnection.java:137)
at com.sun.star.lib.connections.pipe.pipeConnector.connect(pipeConnector.java:145)
at com.sun.star.comp.connections.Connector.connect(Connector.java:146)
at com.sun.star.comp.urlresolver.UrlResolver$_UrlResolver.resolve(UrlResolver.java:133)
at com.docmosis.converter.openoffice.BootstrapOpenOfficeConnection.initialise(line:136)
at com.docmosis.converter.openoffice.BootstrapOpenOfficeConnection.(line:102)
at com.docmosis.converter.openoffice.BootstrapOpenOfficeConnection.(line:78)
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.getBootstrapConnection(line:148)
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.getNewConnection(line:129)
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.establishConnection(line:115)
at com.docmosis.converter.openoffice.LocalOpenOfficeConverter.(line:68)
... 9 more
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
INFO: Shutting down terminus
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
INFO: Shutting down
Dec 22, 2009 3:11:05 PM com.docmosis.util.logging.JavaLogger log
INFO: Shutdown initiated

Top
December 24, 2009 at 5:19 am
#6
admin
Offline
Joined: 2010-09-06
Check Open Office

What version of OpenOffice are you running? Can you launch Open Office by itself successfully?

Top
December 30, 2009 at 5:16 am
#7
rustyspoone
Offline
Joined: 2010-06-23
Open Office Version

I am using OpenOffice 2.4.0 as recommended (or rather required and limited to...). And, no, it does not start up. Nearly two years ago I first loaded OpenOffice onto this machine. It was crap. When opening the application X11 would start up. It would hang there and OpenOffice would not start until I closed X11 (and only at the right time). So I used NeoOffice instead.

6 months or so ago OpenOffice finally released a version that was usable on the Mac (version 3.1.0). Gleefully I installed it and no longer have to use NeoOffice.

Now for this project we are looking at using Docmosis. I need to revert to some older version of OpenOffice in order to run Docmosis? I have since upgraded my machine to Snow Leopard. Now the older OpenOffice 2.4.0 will not even run. Docmosis will not work with the newer 3.1.0. That pretty much puts an end to Docmosis. Docmosis looked very promising. But it seems my only options are to use a Windows machine or go with some other solution. I will try this on Windows first. I sure hope it works.

Now I have all kinds of concerns about having to configure this for our production machines. The versions of OpenOffice supported for Windows, Linux and Mac are all wildly different. I can remove Mac from the equation. But if I develop and test in Windows, what differences will there be in a Linux production environment?

As much as Docmosis seems like a great product, why would they lock themselves into requiring such a poorly supported product. Maybe I am missing something here, being new to Docmosis. But frankly, the dependency on OpenOffice really stinks.

Top
December 30, 2009 at 9:56 am
#8
admin
Offline
Joined: 2010-09-06
Mac options and other considerations
Hello rustyspoone. Well, it looks like you're covering all bases - MacOS, Linux and Windows. This is good because you can have systems running wherever you like, and bad because you'll always have environmental differences to deal with. With regards to Mac, it appears the new version of OpenOffice (3.2) which was due out in December (but probably now in January 2010) is available for Mac and will be supported by Docmosis. This is great news for us since we really want to be compatible with the latest version of OpenOffice - it is just that versions 3.0.1 and onwards have some bugs which we consider unacceptable for Docmosis (see the known issues table). You might find that the issues listed are not a problem for and you can happily use version 3.1.0. We are still evaluating and making adjustments to Docmosis to work with OpenOffice 3.2 and we plan to release the new version of Docmosis before OpenOffice 3.2 is officially released. With regards to building systems for production environments, we recommend you have your dev, test and production platforms as similar as possible. Of course this is not always possible but as long as your test and production environments match and you can do enough good testing, you can typically develop on whatever platform suits you best. Many Docmosis users are developing on Windows and deploying on Linux. Windows and Linux environments have proven to be highly consistent as far as cross-development with Docmosis goes since the required versions of Java, OpenOffice and Docmosis are consistent across Windows and Linux in general. The biggest issue you will have when moving between platforms is FONTS. You will need to ensure that the fonts used in your Docmosis templates are available on all systems where the template will be used (that means where the Docmosis and the Docmosis Converters run). If not, you will get subtle differences in page counts, alignment etc since missing fonts are substituted on a best-effort basis during processing and this effect might not be visible depending on your setup. For example say you have a Word document as your Docmosis template with the Arial font in it. You then render this template on a Linux system which doesn't have the Arial font and produce a Word document result. If you then view the resulting document on Windows again, the Arial font will be available to view the document, but since it wasn't available on the Linux system where you rendered it, the document may have subtle issues. The types of problems you can expect when font differences occur are:
  1. Layout is slightly incorrect
  2. Table Of Contents (indexes etc) numbering doesn't match the actual page numbers
  3. Page Counts are incorrect
  4. The PDF result doesn't match closely to the DOC or ODF result
On Linux, various font packs are available so you should install any that you require. We're glad you think Docmosis seems like a great product. For better or worse it is highly dependent on OpenOffice for document production. OpenOffice is a great tool and can do things Docmosis itself could never do directly. Hopefully the information above, and the new version of OpenOffice that is due out very soon will smooth things out for you.
Top
May 12, 2010 at 4:20 am
#9
rustyspoone
Offline
Joined: 2010-06-23
RE: Mac options and other considerations

I am happy to say that I am back on this project after many weeks of being taken off to do other work.

I was very happy to see that there were newer version of OpenOffice and Docmosis. I removed all older version of OpenOffice from my Mac. I installed OO 3.2. I downloaded the most recent version of Docmosis (2.0).

The examples run fine.

Yay!

Top
May 12, 2010 at 8:16 pm
#10
modman
Offline
Joined: 2010-11-25
Thanks for the Feedback

Hi Rustyspoone.

Thanks for the feedback. 2.2.1 is due out presently with some fixes to non-List Java collection reflection.

Top