On 11/12/2011 03:09 PM, Christian Ehrlicher wrote:
Ok, next step - is it correct that I don't need a custom rdb anymore? The
example formerly created an own rdb but is now using offapi.rdb from basis-
link/program
The old rdb creation procedure also used some libs which are not there anymore
- remotebridge.uno.so and bridgefac.uno.so
Conceptually, there are two kinds of rdbs, those for types and those for
services. For types, LibO itself uses a types.rdb in the URE layer (for
the general URE types) and an offapi.rdb in the basis layer (for the
office-suite-specific types). For services, LibO similarly uses a
services.rdb in the URE layer and one in the basis layer.
Now when I try to use the provided rdb I get an error when I try to load a
document:
"LoadFromUrl failed: Binary URP bridge disposed during call -
file:///home/chehrlic/Dokumente/test.odp"
Out of curiosity the documentloader example can load my document and I can't
find a difference between the example and my code.
"Binary URP bridge disposed during call" indeed hints at broken
plumbing, like the two ends of the bridge using different type
descriptions (which appears unlikely if you use the offapi.rdb from
LibO's basis layer---together with the types.rdb from LibO's URE layer)
or something like that.
The easiest would be if you presented a (stripped down) version of your
failing code. It might be that you fail to include the URE's types.rdb,
for example.
Stephan
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.