[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.technology.equinox] Re: Question regarding ServiceSelector Filter mechanism
|
Hm,
I think you have a valid use case, but our end user's use case is as
valid as the one that you describe. So the filter approach solves one
problem by bringing in a problem that didn't exist before. To me it
seems not a good strategy to make the usage of Equinox on the serverside
more popular by suggesting to our users to patch bundles to solve such
problems.
I would prefer an approach e.g. that allows to declare such filters
independently from the servlet/resources registration. This would solve
the problem you describe and still allows people to use the help.webapp
bundle.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Gunnar Wagenknecht [mailto:gunnar@xxxxxxxxxxxxxxx]
Bereitgestellt: Montag, 21. Juli 2008 17:48
Bereitgestellt in: eclipse.technology.equinox
Unterhaltung: Question regarding ServiceSelector Filter mechanism
Betreff: Re: Question regarding ServiceSelector Filter mechanism
Hi Frank,
Frank Appel schrieb:
> problems. Anyway it would be nice if somebody could point me to more
> detailed information or solution regarding this problem.
I'm afraid you need to patch the help plug-in to register with *any*
HttpService available (or use an alternate filter if necessary).
> 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.
I can't comment on why it was introduced the first time. However, I have
a use case. I'm developing a platform which provides multiple
HttpService instances. One is for "public" stuff and the other for
"admin" stuff. Think of it as an admin/system back office which - in
addition to being password protected - must also be hidden from the
public port.
Yet another use case might be virtual hosting or SSL sites. Some content
should only be available over an SSL connection.
FWIW, I actually patched RAP to only register with a specific service
instance. This works well for the actual servlet but not for the
resources.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=241210
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/