Does exist any mechanism to avoid that? Otherwise special care
should be taken specially on servlets.
I understand the HTTP Registry bundle is right now a very simple
one, but I think it should take into account the state of other bundles to
register/unregister the resources.
Thanks!
Juan
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Thursday, February 08, 2007 7:11 PM
To: Equinox development mailing list
Cc: equinox-dev@xxxxxxxxxxx; equinox-dev-bounces@xxxxxxxxxxx
Subject: Re: [equinox-dev] Unregistering resources
usingorg.eclipse.equinox.http.registry
Yes because the
extensions contained in the plugin.xml are added to the registry as soon as the
bundle is in the resolved state and they are only removed when the bundle is
uninstalled.
PaScaL
|
"Juan
M. Wajnerman" <jwajnerman@xxxxxxxxxxxx>
Sent by:
equinox-dev-bounces@xxxxxxxxxxx
02/08/2007
05:05 PM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
|
|
To
|
equinox-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
|
[equinox-dev]
Unregistering resources using
org.eclipse.equinox.http.registry
|
|
Hi,
I’m using
org.eclipse.equinox.http.registry to expose some resources from a bundle. The
issue I found is that when that bundle is stopped (from console) the resources
continue being available. Is that the expected result? Note that servlets can
continue running.
I also tried to
configure the bundle to not to start when the framework starts, but the
resources are already registered before I manually start the bundle.
Thanks,
Juan Wajnerman_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
