Marten,
Marten Feldtmann wrote:
I've difficulties with this thinking. The structure of an object
is always defined - regardless of a context. The initialization
may be not possible without an context - but the structure should
be always there.
??? Could elaborate somewhat?
And the questions are still the same:
- WHAT is a usable context of theTypeDescriptionManager ?
A com.sun.star.uno.XComponentContext gets typically passed to the
constructor of your object.
- How do I get the singleton of theTypeDescriptionManager ?
Just ask the originally passed XComponentContext for it:
Any any(xComponentContext.getValueByName(
rtl::OUString(RTL_CONSTASCII_USTRINGPARAM(
"/singletons/com.sun.star.reflection.theTypeDescriptionManager"
)
)
);
And if one have 6 different ways to get different meta information
about objects I would ask myself: why ?
So, there _is_ some overlap between the TypeDescriptionManager/Provider
and the CoreReflection (mostly for historical reasons), but this overlap
is not _too_ big. The TypeDescriptionManager/Provider stuff is easier to
use, a very small subset of the CoreReflection functionality and AFAIK
the only way to retrieve _all_ types, including services descriptions.
It is used at the lowest levels (e.g. marshalling).
the next question comes to my mind: how do I get the information
if one service is using the "multiple inhertitance" stuff.
Multiple inheritance interfaces are just like all ordinary UNO
interfaces and much easier to handle, especially compared to service
descriptions. So, you actually _do_ _not_ _need_ XServiceInfo anymore,
in case your object is implemented by using multiple inheritance.
Multiple inheritance replaces the classical interface aggregation
originally done with service descriptions.
Actually I thought, that the whole stuff is easy:
- Interfaces have methods, properties, structs, enumerations, exceptions
Interfaces support methods and attributes only ...
- Services can support multiple interfaces
They can.
- Singletons are instances of Services, which should only
exists once.
No, singletons are special (registered at the component context)
instances of services.
Marten
Hope that helps
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
