Reminder: region is a concept which allows partitioning the OSGi framework
between multiple defined regions and control the visibility of bundles,
packages and services while crossing regions. This allow the same bundle
to be deployed in two different regions if the regions can't see each other
Hi Guillaume,
thanks for the Head-up. The first time I had contact with some sort of
region was while playing around with the spring-dm-server (now Virgo) and
tbh. I didn't like it.
Especially this separation of kernel- and user-land for bundles been a big
pita and quite confusing,
the worst
Hi Achim,
as far as I understood the concept regions control visibility of bundles.
So when for example the spring 2 bundles are visible in a region then
the resolver will wire bundle imports to them. If they are not visible
the resolver does not wire them.
So I think the classloading is not
Yes, you're right about a lot of things.
Regions end up creating some kind of hierarchical classloader tree similar
to JEE.
In theory, regions define a graph, not a tree, but it's quite difficult to
manage from a user pov, so limiting to a tree makes things easier imho.
Using a graph instead of a
Hi,
building the latest 3.0.2-SNAPSHOT did work right away, it only failed for
a integration test, but we had some issues with that during the release
also. Master I didn't test yet.
regards, Achim
2014-04-15 23:36 GMT+02:00 Krzysztof Sobkowiak krzys.sobkow...@gmail.com:
Hi
I'm trying to
+1000 for removing the existing region support I added before the subsystems
spec was ready.
I don't understand why you want to do the rest. Could you elaborate on what
your proposal does that can't be done with spec subsystems? Also, what tooling
is missing for spec subsystems?
I always
I just test @MultipartConfig on Karaf 3.0.1.
It's works! Thank you!
--
View this message in context:
http://karaf.922171.n3.nabble.com/Annotation-processing-in-war-deployed-to-karaf-3-0-0-tp4031937p4032847.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Awsome :)
been a pleasure :)
2014-04-17 20:16 GMT+02:00 lis0x90 lis0...@gmail.com:
I just test @MultipartConfig on Karaf 3.0.1.
It's works! Thank you!
--
View this message in context:
I like idea of having regions and/or subsystens. We currently run multiple
applications and layering” of some things would work great for us. Now
services published by one bundle might be consumed by any other module which is
fine but very relax. For example database connection should not be
Here are a few missing things that are supported with features and not
subsystems (api or impl), roughtly sorted from less important to more
important. The first point is really an implementation limitation, the
others are more related to the spec.
* missing configurations support
* missing
10 matches
Mail list logo
