Getting a Service Manager

OpenOffice.org Developer's Guide

Professional UNO

< Previous Section

Next Section >

• Introduction
• API Concepts

• Data Types

• Simple Types
• The Any Type
• Interfaces
• Services
• Structs
• Predefined Values
• Sequences
• Modules
• Exceptions
• Singletons

• Understanding the API Reference

• UNO Concepts

• UNO Interprocess Connections

• Starting OpenOffice.org in Listening Mode
• Importing a UNO Object
• Characteristics of the Interprocess Bridge
• Opening a Connection
• Creating the Bridge
• Closing a Connection
• Example: A Connection Aware Client

• Service Manager and Component Context

• Service Manager
• Component Context

• Using UNO Interfaces
• Properties
• Collections and Containers
• Event Model
• Exception Handling
• Lifetime of UNO objects

• acquire() and release()
• The XComponent Interface
• Children of the XEventListener Interface
• Weak Objects and References
• Differences Between the Lifetime of C++ and Java Objects

• Object Identity

• UNO Language Bindings

• Java Language Binding

• Getting a Service Manager
• Transparent Use of Office UNO Components
• Handling Interfaces
• Type Mappings

• Mapping of Sequence Types
• Mapping of Enum Types
• Mapping of Struct Types
• Mapping of Exception Types
• Mapping of Interface Types
• Mapping of UNOIDL
• Mapping of Services
• Mapping of Singletons
• Inexact approximation of UNO Value Semantics

• C++ Language Binding

• Establishing Interprocess Connections
• Transparent Use of Office UNO Components
• Type Mappings

• Mapping of Struct Types
• Mapping of Interface Types
• Mapping of Sequence Types
• Mapping of Services
• Mapping of Singletons

• Using Weak References
• Exception Handling in C++

• OpenOffice.org Basic

• Handling UNO Objects

• Instantiating UNO Services
• Getting Information about UNO Objects

• Mapping of UNO and Basic Types

• Mapping of Simple Types
• Mapping of Sequences and Arrays
• Mapping of Structs
• Mapping of Enums and Constant Groups

• Case Sensitivity
• Exception Handling
• Listeners

• Automation Bridge

• The Service Manager Component
• Using UNO from Automation

• Calling Functions and Accessing Properties
• Return Values
• Usage of Types

• Using Automation Objects from UNO
• Type Mappings

• Default Mappings

• Mapping of Simple Types
• Mapping of Hyper and Decimal
• Mapping of String
• Mapping of Interfaces and Structures
• Mapping of Sequence
• Mapping of Type

• Conversion Mappings
• Client-Side Conversions
• Value Objects
• Exceptions and Errorcodes

• Automation Objects with UNO Interfaces
• DCOM
• The Bridge Services
• Unsupported COM Features

• CLI Language Binding

• The Language Binding DLLs
• Type Mapping

• Type Name Decoration
• Type Mappings
• Additional Structures

• Lifetime Management and Obtaining Interfaces
• Writing Client Programs

• The Override Problem
• Important Interfaces and Implementations

< Previous Page

Next Page >

Office objects that provide the desired functionality are required when writing a client application that accesses the office. The root of all these objects is the service manager component, therefore clients need to instantiate it. Service manager runs in the office process, therefore office must be running first when you use Java components that are instantiated by the office. In a client-server scenario, the office has to be launched directly. The interprocess communication uses a remote protocol that can be provided as a command-line argument to the office:

 soffice -accept=socket,host=localhost,port=8100;urp

The client obtains a reference to the global service manager of the office (the server) using a local com.sun.star.bridge.UnoUrlResolver. The global service manager of the office is used to get objects from the other side of the bridge. In this case, an instance of the com.sun.star.frame.Desktop is acquired:

  import com.sun.star.uno.XComponentContext;
  import com.sun.star.comp.helper.Bootstrap;
  import com.sun.star.lang.XMultiComponentFactory;
  import com.sun.star.bridge.UnoUrlResolver;
  import com.sun.star.bridge.XUnoUrlResolver;
  import com.sun.star.beans.XPropertySet
  import com.sun.star.uno.UnoRuntime;
 
  XComponentContext xcomponentcontext = Bootstrap.createInitialComponentContext(null);
 
  // create a connector, so that it can contact the office
  XUnoUrlResolver urlResolver = UnoUrlResolver.create(xcomponentcontext);
 
  Object initialObject = urlResolver.resolve(
      "uno:socket,host=localhost,port=8100;urp;StarOffice.ServiceManager");
 
  XMultiComponentFactory xOfficeFactory = (XMultiComponentFactory) UnoRuntime.queryInterface(
      XMultiComponentFactory.class, initialObject);
 
  // retrieve the component context as property (it is not yet exported from the office)
  // Query for the XPropertySet interface.
  XPropertySet xProperySet = (XPropertySet) UnoRuntime.queryInterface( 
      XPropertySet.class, xOfficeFactory);
 
  // Get the default context from the office server.
  Object oDefaultContext = xProperySet.getPropertyValue("DefaultContext");
 
  // Query for the interface XComponentContext.
  XComponentContext xOfficeComponentContext = (XComponentContext) UnoRuntime.queryInterface(
      XComponentContext.class, oDefaultContext);
 
  // now create the desktop service
  // NOTE: use the office component context here!
  Object oDesktop = xOfficeFactory.createInstanceWithContext(
       "com.sun.star.frame.Desktop", xOfficeComponentContext);

As the example shows, a local component context is created through the com.sun.star.comp.helper.Bootstrap class (a Java UNO runtime class). Its implementation provides a service manager that is limited in the number of services it can create. The names of these services are:

• com.sun.star.lang.ServiceManager
• com.sun.star.lang.MultiServiceFactory
• com.sun.star.loader.Java
• com.sun.star.loader.Java2
• com.sun.star.bridge.UnoUrlResolver
• com.sun.star.bridge.BridgeFactory
• com.sun.star.connection.Connector
• com.sun.star.connection.Acceptor

They are sufficient to establish a remote connection and obtain the fully featured service manager provided by the office.

Content on this page is licensed under the Public Documentation License (PDL).