/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /************************************************************************* * * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * Copyright 2000, 2010 Oracle and/or its affiliates. * * OpenOffice.org - a multi-platform office productivity suite * * This file is part of OpenOffice.org. * * OpenOffice.org is free software: you can redistribute it and/or modify * it under the terms of the GNU Lesser General Public License version 3 * only, as published by the Free Software Foundation. * * OpenOffice.org is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Lesser General Public License version 3 for more details * (a copy is included in the LICENSE file that accompanied this code). * * You should have received a copy of the GNU Lesser General Public License * version 3 along with OpenOffice.org. If not, see * * for a copy of the LGPLv3 License. * ************************************************************************/ #ifndef __com_sun_star_lang_XComponent_idl__ #define __com_sun_star_lang_XComponent_idl__ #include //============================================================================= module com { module sun { module star { module lang { published interface XEventListener; //============================================================================= // DocMerge from xml: interface com::sun::star::lang::XComponent /** allows to exclicitly free resources and break cyclic references.

Actually the real lifetime of an 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.

*/ published interface XComponent: com::sun::star::uno::XInterface { //------------------------------------------------------------------------- // DocMerge from xml: method com::sun::star::lang::XComponent::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 notfied objects should release there 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 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). */ void dispose(); //------------------------------------------------------------------------- // DocMerge from xml: method com::sun::star::lang::XComponent::addEventListener /** 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 XComponent::addEventListener call.

@see XComponent::removeEventListener */ void addEventListener( [in] XEventListener xListener ); //------------------------------------------------------------------------- // DocMerge from xml: method com::sun::star::lang::XComponent::removeEventListener /** 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 XComponent::addEventListener */ void removeEventListener( [in] XEventListener aListener ); }; //============================================================================= }; }; }; }; #endif /* vim:set shiftwidth=4 softtabstop=4 expandtab: */