Hi Stephan,
Yes, that makes sense.
According to the specification, region context's bundleContext was meant
for this:
Typically the Region's context bundle would be used to obtain a bundle
> context with the getBundleContext() method, which has a perspective as a
> constituent of the Region.
Hi Jaseem,
If you use the region context bundle for the extender, the extender will
extend its own region and its children, but it will not reach out of the
region. From my perspective this would be the correct semantics for scoped
subsystems, but I am not an expert here.
Let's assume the foll
I was doing some reading myself following Christoph's argument. Should an
extender be aware of events inside a subsystem at all? is it correct
semantic for information to leak out of the region?
On Thu 24 May, 2018, 12:02 PM Stephan Siano, wrote:
> Hi,
>
> I had a look into the OSGi enterprise
Hi,
I had a look into the OSGi enterprise spec (134.9). It says that the bundle
context of the region context bundle is supposed to be used for subsystem
aware extenders, so the idea of implementing this would be to register the
bundle listener for the web extender with the region context bundl
Hi,
One problem with the bundleContext.getBundle(0) call is that it will return
null if pax web is not running in the root subsystem, in that case the
region context would be required instead.
Concerning the composite subsystems:
What happens if the composite subsystem exports servlets and filt
The subsystem we are using is of type COMPOSITE. That means we would like
these subsystem ESAs to use some of our common components and pax.web is
one of them. We mean to share the core components like pax.web, apace camel
to be reusable. Thats our use case.
On Wednesday, May 23, 2018 at 3:23:
Agree with Christoph. I would also recommend to take a look on subsystem and
region.
Regards
JB
Le 23 mai 2018 à 12:07, à 12:07, "'Christoph Läubrich' via OPS4J"
a écrit:
>I would consider using the systembundles bundle context is bad style!
>This would break instantly the whole code in a secu
I would consider using the systembundles bundle context is bad style!
This would break instantly the whole code in a secured OSGi env or would
require to give the extender huge access rights.
Besdie this, it make IMO the subsystem aproach useless, it was meant to
seperate things, if you now ad
Hello,
Currently pax web extenders are not subsystem-aware. The extenders use
BundleTracker/ServiceTracker on their own BundleContext. Events in scoped
subsystems are not visible to these BundleContexts, hence Web bundles
inside such subsystems don't get registered.
We can solve this by trac
