Daniel Boelzle wrote:
Hello Jürgen,
In your example you bootstrap a new fresh Java UNO env. I assume that
the singleton is not registered in this env but when you use the native
bootstrap mechanism or use the context from an office this singleton
should be registered.
This can maybe considered as bug and you can submit one or an request
for enhancement if you want.
I disagree here, the corereflection service is not a mandatory part of
an URE (and currently not implemented for the "pure Java URE" which is
IMO ok).
you are totally right, i was to fast with my comment. I've forgot that
we have only a C++ implementation for the CoreReflection service.
--> no bug ;-)
Juergen
@Ronny G.: Currently, _only_ soffice's native UNO component context
(addressed via remote or not) garantees _all_ OOo services/singletons to
be available. Bootstrapping native UNO from Java makes a lot more
services available, e.g. the corereflection, but there are still a lot
of OOo services not available, or not functional (relying on running
inside soffice, i.e. legacy problems, of course).
-Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
