Provides information about the element.
Provides access to its containing set object.
Allows controlling the lifetime of the element.
Set elements may be added to and removed from the hierarchy at runtime.
They bear user-defined names. They may exist independently, outside any
New set element instances generally are created through members of
if supported, ::com::sun::star::lang::XMultiServiceFactory
on an implementation of SetUpdate. Initially, they are not
contained in a set object and have no meaningful name.
While an instance is not contained in a set object, it is owned by
the client and can be disposed by calling
::com::sun::star::lang::XComponent::dispose(). The name
of the object can freely be changed in that situation though without
When the instance is inserted into a set (this includes replacing an
existing element), ownership is transferred to the container.
While it is contained in the container, clients must not dispose the
object. When inserted, the name of the object is fixed and is used to
identify it within the container. An implementation may support
::com::sun::star::container::XNamed::setName() even in
this case. If it does, changing the name has the same effect of removing
the object (under the old name) and then reinserting it into the same
container (using the new name).
When an instance is removed from a set (this includes being replaced by
a new element), ownership is transferred to the client again. It can then be
disposed or reinserted into a container. An instance can only be inserted
into a container, if it was obtained from the same hierarchy.
When a set element is removed from its set from outside the hierarchy, the
container disposes of the object. This occurrence can be detected by registering
a ::com::sun::star::lang::XEventListener with the object.
If an implementation is part of a read-only view of the hierarchy,
changing the name or parent is not supported (the object can't be removed from
its container anyway).