topic Re: Enterprise 3.0+OpenOffice.org3=No transformations... in Alfresco Archive

Enterprise 3.0+OpenOffice.org3=No transformations...

meansartin14 — Thu, 30 Oct 2008 16:21:57 GMT

Platform/Supporting Apps: Red Hat Enterprise Linux 5.2, MySQL 5.0.45, JDK 1.6.0 Update 7, OpenOffice.org 3, Tomcat 6.0.18 *came with Alfresco Enterprise 3.0 installer*Alfresco Version: Alfresco Enterprise 3.0 (from AlfrescoEnterprise-3.0.0-Linux-x86-Install.bin) *TRIAL*Background:I am developing a p

Re: Enterprise 3.0+OpenOffice.org3=No transformations...

loftux — Thu, 30 Oct 2008 18:07:17 GMT

What does your openoffice-startup-context.xml look like?
Does it work if you manually run this startup command? Run the complete statement that is within the CDATA section.
I would try to remove the quotes if present.
This is what my startup command look like

/usr/lib/openoffice/program/soffice -accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager -env:UserInstallation=file:///home/petl/.openoffice.org2/user -nologo -headless -nofirststartwizard -nocrashrep -norestore‍

I'm running open office with the existing OpenOffice profile (end:UserInstallation) on my local box. I've seen that if you want to use a separate profile location you may need to copy one existing, it does not always succeed to create it.

Re: Enterprise 3.0+OpenOffice.org3=No transformations...

meansartin14 — Thu, 30 Oct 2008 18:43:40 GMT

What does your openoffice-startup-context.xml look like?
Does it work if you manually run this startup command? Run the complete statement that is within the CDATA section.
I would try to remove the quotes if present.

Here's what that section of my openoffice-startup-context.xml file looked like:

<value><![CDATA["/opt/openoffice.org3/program/soffice" "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" "-env:UserInstallation=file:////opt/openoffice.org3" -nologo -headless -nofirststartwizard -nocrashrep -norestore]]></value>[/code]

I removed the quotes, restarted Alfresco and viola… Transformations now appear to work properly!

This should definitely be written into the bug database, if it's not there already.‍‍‍‍‍