Hi Stefan,

thanks for your quick answer :)

Stephan Bergmann a écrit :


> You are probably using com.sun.star.comp.helper.Bootstrap.bootstrap.
> Despite being included in a URE jar, this is OOo-specific functionality,
> so it is by design that it fails for you.  Poor design indeed, I agree...

That's what I thought...

> 1  Start a native process (uno executable) and let it run your Java code
> as an XMain component (see test-javatest in
> ure/source/uretest/Makefile[.pln] for an example).  That way, the uno
> executable takes care of all the UNO bootstrapping and your XMain
> component runs in an environment where the information from types.rdb
> and services.rdb is accessible.

This solution will certainly the best one for the moment, but I'ld like
to switch to the second when the
Bootstrap.defaultBootstrap_InitialComponentContext won't break when
called from a custom ClassLoader.

> 2  Start a Java process that bootstraps a native UNO environment in
> process via
> com.sun.star.comp.helper.Bootstrap.defaultBootstrap_InitialComponentContext
> (see test-javanative in ure/source/uretest/Makefile[.pln] for an
> example).  That way, the returned XComponentContext gives you access to
> an environment where the information from types.rdb and services.rdb is
> accessible.

Good to hear that this is possible: it would be the same way for OOo and
the URE. However as explained upper, there are still some bugs and I'll
wait for them to be fixed on every platform.

> 3  If your are only interested in information about specific UNO types
> from types.rdb, and not the UNO services from services.rdb, some
> information about those types is also available in a plain Java UNO
> environment from com.sun.star.uno.Type (esp. Type.getTypeDescription).

In fact this could be very good for code auto-completion I think, but
not to get a list of all the types as I'm doing.

Thanks for your help,
Cedric

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to