https://bugs.documentfoundation.org/show_bug.cgi?id=166857

--- Comment #2 from Skaret <[email protected]> ---
I did a little research.

If 'NativeBootstrap.defaultBootstrap_InitialComponentContext()' is called after
the regular 'NativeBootstrap.bootstrap()', no error occurs.

This is because 'bootstrap()' from 'core/cppuhelper/source/bootstrap.cxx' that
calls from 'NativeBootstrap.bootstrap()' contains the following code:
if (!Bootstrap::get(u"URE_BOOTSTRAP"_ustr, uri)) {
            Bootstrap::set(
                u"URE_BOOTSTRAP"_ustr,
                Bootstrap::encode(
                    path +
#if defined MACOSX
                    "../Resources/"
#endif
                    SAL_CONFIGFILE("fundamental")));
        }

This code calls 'rtl_bootstrap_set(pName, pValue)' from
'core/sal/rtl/bootstrap.cxx' with parameters similar to these:
pName: "URE_BOOTSTRAP"
pValue: "file:///home/user/core/instdir/sdk/../program/fundamentalrc"

And this is enough to prevent the initial error. Therefore, if you separately
call 'rtl_bootstrap_set(pName, pValue)' with these parameters before
'NativeBootstrap.defaultBootstrap_InitialComponentContext()', everything will
work.

Both methods ('NativeBootstrap.bootstrap()' and
'NativeBootstrap.defaultBootstrap_InitialComponentContext()') are simply
wrappers over methods from the cppuhelper module.
Note that when using 'defaultBootstrap_InitialComponentContext' from C++ (for
example, in the "DocumentLoader.cxx" example), everything works normally and an
additional call to 'rtl_bootstrap_set()' is not required unlike in .NET C#

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to