LibreOffice: XComponent Interface Reference

LibreOffice LibreOffice 7.6 SDK API Reference

Loading...
Searching...
No Matches
Public Member Functions | List of all members
XComponent Interface Referencepublished

allows to explicitly free resources and break cyclic references. More...

`import <XComponent.idl;`

Inheritance diagram for XComponent:

## Public Member Functions
void | dispose ()
| The owner of an object calls this method to explicitly free all resources kept by this object and thus break cyclic references.
void | addEventListener ([in] XEventListener xListener)
| adds an event listener to the object.
void | removeEventListener ([in] XEventListener aListener)
| removes an event listener from the listener list.
Public Member Functions inherited from XInterface
any | queryInterface ([in] type aType)
| queries for a new interface to an existing UNO object.
void | acquire ()
| increases the reference counter by one.
void | release ()
| decreases the reference counter by one.

## Detailed Description

allows to explicitly free resources and break cyclic references.

Actually the real lifetime of a UNO object is controlled by references kept on interfaces of this object. But there are two distinct meanings in keeping a reference to an interface: 1st to own the object and 2nd to know the object.

You are only allowed to keep references of interfaces to UNO objects if you are by definition the owner of that object or your reference is very temporary or you have registered an EventListener at that object and release the reference when "disposing" is called.

Developers Guide
  Professional UNO - Lifetime of UNO objects
  Office Development - Closing Documents
  Writing UNO Components - XComponent
  Writing UNO Components - Core Interfaces to Implement
  Office Development - Using the Component Framework

## Member Function Documentation

## ◆ addEventListener()

void addEventListener | ( | [in] XEventListener | xListener | ) |

adds an event listener to the object.

The broadcaster fires the disposing method of this listener if the XComponent::dispose() method is called.

It is suggested to allow multiple registration of the same listener, thus for each time a listener is added, it has to be removed.

If this XComponent is already disposed when XComponent::addEventListener() is called, the call will not fail with a DisposedException, but the caller will be notified via the XEventListener::disposing() callback. This callback can occur synchronously within the addEventListener() call.

See also
  XComponent::removeEventListener

## ◆ dispose()

void dispose | ( |  | ) |

The owner of an object calls this method to explicitly free all resources kept by this object and thus break cyclic references.

Only the owner of this object is allowed to call this method. The object should release all resources and references in the easiest possible manner ( for instance no serialization should take place anymore ).

The object must notify all registered listeners using the method XEventListener::disposing(). All notified objects should release their references to this object without calling XComponent::removeEventListener() (the disposed object will release the listeners eitherway).

After this method has been called, the object should behave as passive as possible, thus it should ignore all calls in case it can comply with its specification (for instance addEventListener()). Often the object can't fulfill its specification anymore, in this case it must throw the DisposedException (which is derived from com::sun::star::uno::RuntimeException) when it gets called.

For some objects no real owner can be identified, thus it can be disposed from multiple reference holders. In this case the object should be able to cope with multiple dispose()-calls (which are inevitable in a multithreaded environment).

## ◆ removeEventListener()

void removeEventListener | ( | [in] XEventListener | aListener | ) |

removes an event listener from the listener list.

It is a "noop" if the specified listener is not registered.

It is suggested to allow multiple registration of the same listener, thus for each time a listener is added, it has to be removed.

If this XComponent is already disposed when XComponent::removeEventListener() is called, the call will not fail with a DisposedException, but will rather be ignored silently.

See also
  XComponent::addEventListener

The documentation for this interface was generated from the following file:

- com/sun/star/lang/XComponent.idl