|
|
|
Re: Registration of ServiceHandlers [message #52252 is a reply to message #50900] |
Wed, 17 October 2007 10:39   |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
the servicehandler xml files are not parsed due to the classloader
architecture of the OSGi framework. The files are simply not found. Because
of this the servicehandler files are only useful in standalone RWT/W4Toolkit
applications. Currently servicehandlers can only be added programmatically
in RAP applications. To add servicehandlers declaratively in RAP we have to
introduce an extension point. I will add this info to the bug entry.
Ciao
Frank
"Stefan R
|
|
|
|
Re: Registration of ServiceHandlers [message #52865 is a reply to message #52811] |
Thu, 18 October 2007 06:49   |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
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.
Ciao
Frank
"Stefan R
|
|
|
Re: Registration of ServiceHandlers [message #55844 is a reply to message #52865] |
Fri, 26 October 2007 13:22  |
Stefan  Messages: 316 Registered: July 2009 |
Senior Member |
|
|
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)?
Regards,
Stefan.
Frank Appel schrieb:
> Hi,
>
> 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.
>
> Ciao
> Frank
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02565 seconds