It looks like we can even override the class OfficeConnectionMode ourselves and pass it as a parameter to the ExternalProcessOfficeManager constructor. That's the easiest way without needed a special build of officeimport.
I don't think that the fact that it was not done necessarly means it is difficult. The need might just not have been there. Ludovic Asiri Rathnayake a écrit : > Hi, > > On Tue, Apr 28, 2009 at 12:27 PM, Ludovic Dubost <[email protected]> wrote: > > >> Hi Guys, >> >> The class for external processes is already available >> >> >> http://code.google.com/p/jodconverter/source/browse/tags/3.0-beta-2/jodconverter/src/main/java/net/sf/jodconverter/office/ExternalProcessOfficeManager.java >> >> Which basically means you just need to modify this code to call a >> different ProcessOfficeManager >> > > > Yes, but this is for a "external but local" openoffice process (OOo process > running inside the local computer). > > It seems like a small hack into this class: > > http://code.google.com/p/jodconverter/source/browse/tags/3.0-beta-2/jodconverter/src/main/java/net/sf/jodconverter/office/OfficeConnectionMode.java > > would allow us to connect to a remote OOo server (changing accept string). > But I highly doubt that is enough, otherwise mirko would have already > implemented it. > > I will update all of you once I get a chance to look at the code more > closely. > > Thanks. > > - Asiri > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > > -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
