MinGW-Port: Problems with UnoUrlResolver
sbergman at redhat.com
Wed Feb 22 04:01:07 PST 2012
On 02/22/2012 11:53 AM, Helmar Spangenberg wrote:
> My understanding of the whole subject still is too small - I thought,
> once I got the context bootstrapped, the whole communication to the
> office is done by a socket or a pipe.
Yes, but what gets communicated over that pipe is remote procedure
calls, so on the client side you need some code to engage in that remote
procedure calling. And the code that is available for that is either
C++ or Java.
> Is it too naive to think that when the context is available all the
> rest of the communication should work?
Yes, I fear so. Again, the inability to obtain local UnoUrlResolver
service probably indicates a fundamental problem somewhere in the MinGW
UNO stack. (Note that it is not necessarily a big problem, maybe even
only a triviality. But hard to tell w/o an environment to try it out.)
More information about the LibreOffice