Hi Andreas,
If you call registerDispatchProviderInterceptor() the framework will
call setMasterDispatchProvider() and setSlaveDispatchProvider().
Do nothing there excepting caching those two dispatch objects.
From this point your interceptor is part of the double-linked
interceptor chain.
Hi Paolo,
Hi,
Andreas Schlüns ha scritto:
Hi Carlos,
(I'm using Automation Bridge to communicate with OOo)
After reading again all the stuff and trying to digest the java
sample, this is what I conluded:
I need to implement my own DispatchProvider as a COM object an pass
it as a
Hello Andreas,
Andreas Schlüns ha scritto:
Hi Paolo,
[...]
You are right ... it's possible ... but I wouldnt do that !
And I totally agree, but I like so much to find this kind of sneaky
tricks in StarBasic :-)
Why ?
a)
[...]
b)
On the other side I believe you can run into trouble with
Hi Paolo, Carlos, *
Paolo Mantovani escribió:
Hi,
Andreas Schlüns ha scritto:
Hi Carlos,
(I'm using Automation Bridge to communicate with OOo)
After reading again all the stuff and trying to digest the java
sample, this is what I conluded:
I need to implement my own DispatchProvider
(I'm using Automation Bridge to communicate with OOo)
After reading again all the stuff and trying to digest the java sample,
this is what I conluded:
I need to implement my own DispatchProvider as a COM object an pass it
as a parameter to registerDispatchProviderInterceptor, in the same way
