[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] Unregistering resources usingorg.eclipse.equinox.http.registry


Just to point out that the http.registry bundle is explicitly support for contributing to the HTTP Service via the extension registry.  That is why it is called http.registry.  If it used services to contribute, it would just be the HTTP service :-)

For fun, you can also consider contributing the extensions dynamically in your bundle's activator (or elsewhere). The extension registry allows you to call IExtenstionRegistry.addContribution().  You can add your servlets and resources whenever you like.

Jeff



BJ Hargrave <hargrave@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

02/08/2007 06:55 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
RE: [equinox-dev] Unregistering resources        usingorg.eclipse.equinox.http.registry





This is the "risk" of using the extension point registry. It operates at
the module layer of OSGi which means that resolved bundles contribute
regardless of the start/stop state of the bundle. If the http.registry was
based upon the service layer of OSGi, then the start/stop would factor
into the contribution.

So this effectively falls to the design decision to use the extension
point model for contributions in the http.registry.

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx

office: +1 386 848 3788
mobile: +1 386 848 3788




"Juan M. Wajnerman" <jwajnerman@xxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
02/08/2007 05:26 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
cc

Subject
RE: [equinox-dev] Unregistering resources
usingorg.eclipse.equinox.http.registry






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
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev