| [news.eclipse.technology.equinox] Question regarding ServiceSelector Filter mechanism |
|
Hi, doing a follow up on a RAP user complaint regarding that the
eclipse help doesn't work with RAP anymore I came across the ServiceSelector
filter mechanism (bug 158168). It
took me a while to figure out that using '-Dorg.eclipse.equinox.http.jetty.other.info=org.eclipse.help'
as VM argument revives the help system. Unfortunately RAP applications are most often not deployed using
OSGi standalone with the Jetty engine as HttpService provider, they run
embedded in the various available servlet container implementations. So what I
couldn't figure out is what I have to do to bring the help system back to work
in those scenarios (e.g running in tomcat). My hope is that users don't have to
configure a different startup parameter for each container implementation,
since this will cause us user-acceptance problems. Anyway it would be nice if somebody
could point me to more detailed information or solution regarding this problem. By the way something that I couldn't understand properly by reading the bug, is why this functionality was introduced the first time, since it was stated by Simon that ' its quite rare to run more than one HttpService in a single VM'. So I'm wondering if there was a real usecase where the previous situation actually caused problems.
Ciao Frank |