Hi,
On Tue, Jun 17, 2008 at 5:05 PM, Juergen Schmidt
<[EMAIL PROTECTED]> wrote:
> it's up to you to implement a small protocol handler and do the "real" stuff
> on demand. I would decouple the protocol handler from the real functionality
> and would create a new service for it. Later on you can instantiate a new
> object supporting this service on demand ...
> You can provide both implementations (ensure different jars) in the same oxt
> file.
I just found some time to test this approach and it works. But I can't
move with one issue - how to work with new service from another Java
extension? To simplify it, let's say that the service is implemented
in one extension and the menu item in another extension in this case.
My new service extension is installed and I can easily work with it
from Basic (createUnoService(), etc.). It works pretty well, I tested
it.
I tried to use my new service from menu item extension (simple
protocol handler with one menu item). To compile this extension, I
have to include <serviceProject>/dist/IDL_types.jar library.
Otherwise, all interfaces / services are unknown and I can't compile
this extension at all. But when I add IDL_types.jar library to the
menu item extension, I can't install menu item extension. Following
exception occurs ...
(com.sun.star.registry.CannotRegisterImplementationException){{Message
= "", Context = (com.sun.star.uno.XInterface) @0 }}
Any idea what's wrong here? If I want to work with my new service from
another extension, should I add some special entry in extension's XML
files? Or should I include more then IDL_types.jar? Or something else?
I tried this with NetBeans integration module version 1.1.2 (current
CVS snapshot).
--
Robert Vojta
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
