Implementing your own Interfaces

OpenOffice.org Developer's Guide

Writing UNO Components

< {{#switch:Previous Section

Previous Section = Previous Section

Next Section = Next Section

Previous Page = Previous Page

Next Page = Next Page

}}

{{#switch:Next Section

Previous Section = Previous Section

Next Section = Next Section

Previous Page = Previous Page

Next Page = Next Page

}} >

• Required Files
• Using UNOIDL to Specify New Components

• Writing the Specification

• Preprocessing
• Grouping Definitions in Modules
• Simple Types
• Defining an Interface
• Defining a Service
• Defining a Sequence
• Defining a Struct
• Defining an Exception
• Predefining Values
• Using Comments
• Singleton
• Reserved Types
• Published Entities

• Generating Source Code from UNOIDL Definitions

• Component Architecture
• Core Interfaces to Implement

• XInterface
• XTypeProvider
• XServiceInfo
• XWeak
• XComponent
• XInitialization
• XMain
• XAggregation
• XUnoTunnel

• Simple Component in Java

• Class Definition with Helper Class
• Implementing Your Own Interfaces
• Providing a Single Factory Using a Helper Method
• Write Registration Info Using a Helper Method
• Implementing without Helpers
• Storing the Service Manager for Further Use
• Create Instance with Arguments
• Possible Structures for Java Components
• Running and Debugging Java Components

• Register Component File
• Make Registration Available to OpenOffice.org
• Test the Registration
• Debugging
• The Java Environment in OpenOffice.org
• Troubleshooting

• C++ Component

• Class Definition with Helper Template Classes
• Implementing your own Interfaces
• Providing a Single Factory Using a Helper Method
• Write Registration Info Using a Helper Method
• Provide Implementation Environment
• Implementing without Helpers
• Storing the Service Manager for Further Use
• Create Instance with Arguments
• Multiple Components in One Dynamic Link Library
• Building and Testing C++ Components

• Integrating Components into OpenOffice.org

• Protocol Handler

• Implementation
• Configuration
• Installation

• Jobs

• Execution Environment
• Implementation
• Initialization
• Returning Results
• Configuration
• Installation
• Using the vnd.sun.star.jobs: URL Schema
• List of Supported Events

• Add-Ons

• Guidelines
• Configuration

• Menus
• Toolbars
• Images for Toolbars and Menus
• Help Integration

• Installation

• Disable Commands
• Intercepting Context Menus

• File Naming Conventions
• Deployment Options for Components

• Command Line Registry Tools
• Manual Component Installation
• Bootstrapping a Service Manager
• Special Service Manager Configurations

• The UNO Executable

• Standalone Use Case
• Server Use Case
• Using the UNO Executable

• Accessing Dialogs

• Assigning Component Methods to Control Events
• Using Dialogs in Components

< {{#switch:Previous Page

Previous Section = Previous Section

Next Section = Next Section

Previous Page = Previous Page

Next Page = Next Page

}}

{{#switch:Next Page

Previous Section = Previous Section

Next Section = Next Section

Previous Page = Previous Page

Next Page = Next Page

}} >

For the my_module.XSomething interface, add a string to be returned that informs the caller when methodOne() was called successfully.

  OUString MyService2Impl::methodOne( OUString const & str )
      throw (RuntimeException)
  {
      return OUString( RTL_CONSTASCII_USTRINGPARAM(
          "called methodOne() of MyService2 implementation: ") ) + str;
  }

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