Re: [xwiki-users] Open Office import plugin is not working in XEM 2.4.3

Hi everybody, I have XEM 2.3 working in a test environment with OpenSuse 11.3, Mysql 5.1, OpenOffice 3.2.1, and Jetty, as per defualt war distributed, and everything is working fine. I made the upgrade to XEM 2.4.3 version, importing new xar, also. I made modifications to the relevant xwiki.properties file to make the Office importer section identical to the previous 2.3 version, (see below) but the office server does not start and import is not working in 2.4.3! ------ xwiki.log file: (XEM 2.4.3) 2010-10-18 11:23:05,125 [main] ERROR rnal.DefaultObservationManager - Fail to send event [org.xwiki.observation.event.ApplicationStartedEvent@1d592a] to listener [org.xwiki.officeimporter.internal.openoffice.OpenOfficeManagerLifecycleListener@c8e4de] java.lang.IllegalStateException: invalid templateProfileDir: /home/smg/.ooo3/user at org.artofsolving.jodconverter.office.DefaultOfficeManagerConfiguration.buildOfficeManager(DefaultOfficeManagerConfiguration.java:122) at org.xwiki.officeimporter.internal.openoffice.DefaultOpenOfficeManager.initialize(DefaultOpenOfficeManager.java:102) at org.xwiki.officeimporter.internal.openoffice.DefaultOpenOfficeManager.start(DefaultOpenOfficeManager.java:135) at org.xwiki.officeimporter.internal.openoffice.OpenOfficeManagerLifecycleListener.startOpenOffice(OpenOfficeManagerLifecycleListener.java:96) at org.xwiki.officeimporter.internal.openoffice.OpenOfficeManagerLifecycleListener.onEvent(OpenOfficeManagerLifecycleListener.java:83) at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:269) at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:243) at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:290) at org.xwiki.container.servlet.XWikiServletContextListener.contextInitialized(XWikiServletContextListener.java:76) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548) at org.mortbay.jetty.servlet.Context.startContext(Context.java:136) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.mortbay.start.Main.invokeMain(Main.java:194) at org.mortbay.start.Main.start(Main.java:534) at org.mortbay.start.Main.start(Main.java:441) at org.mortbay.start.Main.main(Main.java:119) -------- Since it is a test environment, I can easily start/stop Jetty container and choose to use 2.3 or 2.4.3 versions, which are in different dirs but they use the same database. Since the values of the parameters in the Office import section of the xwiki.properties are exactly the same and if I use 2.3 version Office server starts and import works fine, I wonder if this is a bug of version 2.4.3 or what can be my mistake in configuration. ----------- xwiki.properties file: (good for 2.3 , bad for 2.4.3) # Settings for the OpenOffice server instance consumed by the OfficeImporter plugin #---------------------------------------------------------------------------------- #-# [Since 1.9M2] #-# Type of the openoffice server instance used by officeimporter plugin. #-# 0 - Internally managed server instance. (Default) #-# 1 - Externally managed (local) server instance. # openoffice.serverType=0 #-# [Since 1.9M2] #-# Port number used for connecting to the openoffice server instance. #-# Default port is 8100 # openoffice.serverPort=8100 #-# [Since 1.9M2] #-# If the openoffice server should be started / connected upon XE start. #-# Default value is false openoffice.autoStart=true #-# [Since 1.8RC3] #-# Path to openoffice installation (serverType:0 only). #-# If no path is provided, a default value will be calculated based on the operating environment. openoffice.homePath=/usr/lib/ooo3 #-# [Since 1.8RC3] #-# Path to openoffice execution profile (serverType:0 only). #-# If no path is provided, a default value will be calculated based on the operating environment. openoffice.profilePath=/home/smg/.ooo3/user #-# [Since 1.8RC3] #-# Maximum number of simultaneous conversion tasks to be handled by a single openoffice process (serverType:0 only). #-# Default value is 50 # openoffice.maxTasksPerProcess=50 #-# [Since 1.8RC3] #-# Timeout for conversion tasks (in miliseconds) (serverType:0 only). #-# Default value is 30 seconds # openoffice.taskExecutionTimeout=30000 ----- NOTES: if I comment the line of 'openoffice.profilePath=' the server does not start either, since it takes a default dir that really does not exist. From documentation, I found out that 2.3 uses 'JODConverter 3.0 beta2' , while 2.4.3 uses 'JODConverter 3.0 beta3'; the log messages from 2.3 refer to 'net.sf.jodconverter.office......' while 2.4.3 refer to 'org.artofsolving.jodconverter.office......'. Is this the problem? Hot to configure correctly the new jdoconverter? Thanks for your help Angelo