Thanks for your response Richard.
Basically here is a description of what I want to achieve. I am
developing a OSGi based web gateway for sensors and other devices. For
this purpose, I have the following modules:
1. aparat-core - main library, OSGi-zed. This one can be used
separately for other (also non OSGi) projects as it contains the main
concepts and base classes. As so it does not contain any services or
service interfaces.
2. aparat-services - main service interfaces bundle. One can take the
aparat-core, the aparat-services and the aparat-configurator and
implement another version of the whole gateway. Does not contain
service implementations.
3. aparat-configurator - bundle that implements configuration
management interface exposed in the aparat-services bundle.
4. aparat-registry - bundle that implements persistency management
interface exposed in the aparat-services bundle. Requires aparat-
configurator services to be loaded before providing its own services.
etc. etc.
For some reason, when I start Apache Felix, aparat-registry gets
started before aparat-configurator. Because of that it does not load
aparat-configurator and cannot load its own further.
So I have to stop the aparat-registry bundle and start it again. Then
everything is ok.
So if I would indicate the start levels, I would not go into this
problem.
Any ideas and advices?
Below is the output of my ps command.
START LEVEL 6
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (2.0.0)
[ 1] [Active ] [ 5] org.htmlparser 1.6 [osgi] (1.6)
[ 2] [Active ] [ 5] db4o-java5 7.4.106.13438 [osgi]
(7.4.106.13438)
[ 3] [Active ] [ 5] Apache Felix Configuration Admin Service
(1.2.4)
[ 4] [Active ] [ 5] Apache Felix Log Service (1.0.0)
[ 5] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-core
[ch.ethz.inf.vs.aparat.core] (0.0.1.SNAPSHOT)
[ 6] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-
services [ch.ethz.inf.vs.aparat.services] (0.0.1.SNAPSHOT)
[ 7] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-server
[ch.ethz.inf.vs.aparat.server] (0.0.1.SNAPSHOT)
[ 8] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-
registry [ch.ethz.inf.vs.aparat.registry] (0.0.1.SNAPSHOT)
[ 9] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-
configurator [ch.ethz.inf.vs.aparat.configurator] (0.0.1.SNAPSHOT)
[ 10] [Active ] [ 5] ch.ethz.inf.vs.aparat.build.aparat-rest-
framework [ch.ethz.inf.vs.aparat.rest.framework] (0.0.1.SNAPSHOT)
[ 11] [Active ] [ 1] Apache Felix Shell Service (1.4.0)
[ 12] [Active ] [ 1] Apache Felix Shell TUI (1.4.0)
Regards,
Vlatko
On Oct 4, 2009, at 7:58 PM, Richard S. Hall wrote:
On 10/4/09 19:06, Vlatko Davidovski wrote:
Thanks Filippo!
This was helpful! And would be not great to update the Wikipedia
article, as many people might look into it.
It is bad enough having to maintain our own documentation, but ok, I
did it. :-)
One more question, is there an easy way to indicate the order in
which the bundles are loaded?
Well, you shouldn't do this in general, so we will all look down on
you if you do it, but the only way to truly guarantee it is by
assigning start levels to bundles, but still don't do it. :-)
Better off making your bundles order independent.
-> richard
BR,
Vlatko
On Oct 4, 2009, at 7:00 PM, Filippo Diotalevi wrote:
On Sun, Oct 4, 2009 at 6:48 PM, Vlatko Davidovski <[email protected]
> wrote:
Hi!
A simple question, how can I list the available and registered
services in
Apache Felix 2.0.
Hi,
since Felix Shell 1.4 (shipped with the Felix 2.0.0 distribution)
the "service" command has been replaced by the "inspect" command.
To see the services exposed by a bundle, type
$ inspect service capability <bundle-id>
or in brief
$ inspect s c <bundle-id>
To see services used by a bundle, type
$ inspect service requirement <bundle-id>
or in brief
$ inspect s r <bundle-id>
You can avoid to specify the <bundle-id>, in that case you will see
services (exposed or used) by all the bundles.
--
Filippo Diotalevi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
