Improve OfficeManagers API for specifying socket or pipe connections

[GoogleCodeExporter]

Currently both ManagedProcessOfficeManager and ExternalProcessOfficeManager
accept a free form string for specifying connection parameters.

This is not very clear and error prone. One user for example tried to
connect to OOo on a different host, which shouldn't be possible.

Original issue reported on code.google.com by mirko.na...@gmail.com on 25 Jan 2009 at 2:13

[GoogleCodeExporter]

Introduced class OfficeConnectionMode to encapsulate UNO connection type and 
parameters.

OfficeManager constructors have changed to use the new type. Examples using the 
new API:

OfficeManager officeManager = new
ManagedProcessOfficeManager(OfficeConnectionMode.port(8100));

OfficeManager officeManager = new
ManagedProcessOfficeManager(OfficeConnectionMode.pipe("jodconverter"));

Default constructors have been removed to force users to be aware that e.g. a 
TCP
port will be required.

Original comment by mirko.na...@gmail.com on 25 Jan 2009 at 4:17

• Changed state: Fixed
• Added labels: Priority-Medium

[GoogleCodeExporter]

Fixed in r66

Original comment by mirko.na...@gmail.com on 25 Jan 2009 at 4:17

[GoogleCodeExporter]

Issue 20 has been merged into this issue.

Original comment by mirko.na...@gmail.com on 15 Feb 2009 at 2:03

[GoogleCodeExporter]

Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 1:21

• Changed state: Released