19 May
2009
19 May
'09
6:26 p.m.
Hi Raff,
I think the big problem is not to share an OpenOffice server between
clients (This will be great, but I don't think
it's the most urgent)
IMO, the real problem we have is a security problem: By having XWiki
starting external applications you can't have your tomcat chrooted
nor running on a noexec partition for example.
With XE 1.8.4 you can configure XE to use a separate OOo server process (i.e
not allow XE to manage the OOo server). But still, that server process needs
to be running on the same host as XE.
I think the most urgent is to permit to give an IP and port to the
plugin rather than a directory to the OOo
executables.
Having another servlet container is ok for me, but we should anyway
permit to give a IP and port in the XWiki conf for an OOo server.
How about simply giving the path to the remote servlet? be it local or
remote. This way converter-servlet (and the associated openoffice server)
can be launched and managed independantly from the XE instance. Won't this
solve the security problem you mentioned?
Thanks.
- Asiri