I've been cleaning up my regions code in hopes of committing it shortly, and
just pushed the current version to github (https://github.com/djencks/karaf)
(region branch).
After seeing 3 regression tests fail I discovered that karaf won't start under
equinox when the region jar is installed.
I just opened an issue for a new design of the service:list command. The
idea is to focus on service instead of bundle on the first level.
https://issues.apache.org/jira/browse/KARAF-1077
Any feedback is very welcome.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source
After reading the proposal the third time I really start to like it.
Finally being able to search for features would be definitely great :-) In
addition it would be a single entry point command for services. So, here's
my big +1.
Kind regards,
Andreas
On Fri, Dec 2, 2011 at 12:23,
Hi Glen,
it is about OSGi services. Bundles can offer or use Services.
In my first Karaf Tutorial I show how to provide and consume services:
http://www.liquid-reality.de/display/liquid/2011/02/15/Karaf+Tutorial+Part+1+-+Installation+and+First+application
Basically a service is a Java object
Oh, thanks for the tutorial, I was unaware of the export and ls
commands. LSNED I guess.
Anyway, question, as a result of your proposal, when I enter list at
the Karaf command prompt -- what will I receive, what you're proposing
to rename bundles:list (what we presently see by default), or
Hey,
What about bundle:services bundle-id? The service:list command shows all
services from whole OSGi registry, but what *if* somebody wan'ts to check one
bundle for services used or registered? That's typical case during development.
Regards,
Lukasz
OK, so you're just creating an enhanced
Hi all,
The assemblies are broken this morning (on runtime):
ERROR: Bundle org.apache.aries.blueprint.jexl.evaluator [9] Error
starting
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.jexl.evaluator/0.1.0
(org.osgi.framework.BundleException: Unresolved constraint in bundle
I made a first fix to include commons-jexl (requirement by aries
blueprint jexl evaluator) in the startup.properties, with the correct
start level.
Now, I have another issue with jaas module. I fix it.
@David, did you succeed to run Karaf with blueprint individuals ? I
guess that you didn't
