OSGi uses a service-oriented architecture: Bundles register maintenance objects that consume other packages. Publishing and linking management is structured. This completely disconnects service providers from service users (except for the need to agree on a service interface).
Is there a way to limit (by configuration) which services are visible for which packages?
For example, if I have an HttpService, all packages that want to do this can install servlets in it. I would like to make the HttpService invisible to custom packages.
Additional loans: in addition to filtering the registration of services, you can change the registration properties. Thus, even if the package registers the servlet with alias=/admin, I can change it to alias=/somethingelsefor use on the Pax Web Extender board.
Thilo source
share