|Re: Registration of ServiceHandlers [message #55844 is a reply to message #52865]
||Fri, 26 October 2007 13:22
Registered: July 2009
Frank, you're right, the Activator approachs works. I tried this once |
some weeks ago and got an exception, which doesn't happen by now.
The only problem is, that some plugins are lazy loaded when one class of
them is accessed the first time. Is there a way to specify, that all
available plugins should be loaded at application startup (and so, all
activators are called)?
Frank Appel schrieb:
> from looking at the code I don't know why that Activator approach didn't
> work, since there is only an access to a class variable holding a map. Maybe
> the RWT bundle wasn't activated so that the class could not be found.
> Anyway, one trick could be to use a one-time phaselistener if it is
> sufficient to have the additional service handler running after the first
> request of any client has taken place.
> But actually I don't think that this a good solution for concurrency
> reasons. As an alternative you could register an extra servlet at the http
> service of OSGi. That's not much different to the service handler approach
> of RWT. Instead working with request-parameters you would have to address a
> different servlet with your requests.
> Hope that helps.
Powered by FUDForum
. Page generated in 0.02329 seconds