Hi Christian,
did you try to set the impl as private ?
I don't exactly remember what Karaf scr:list command does (I gonna
check), but it's maybe just a question of display.
Regards
JB
On 02/17/2014 10:10 AM, Christian Schneider wrote:
This weekend I ported one of my examples from blueprint to declarative
services.
See https://github.com/cschneider/Karaf-Tutorial/tree/master/db/command2
While it worked pretty well in general I have one concern with DS about
public services vs internal component wiring.
In my example I intended to export the components implementing Action to
be exported as OSGi services as these have to be picked up by a karaf
module. This worked fine of course.
On the other hand I have some internal components like DbAccess and
DbSelect that I simply wanted to wire into my public services but that
should not be public.
In blueprint I have a clear separation there. Only the beans I export
with a service element are visible to the outside. For DS I have not
found such a feature.
How can I achieve the same hiding of internals in DS? I can imagine that
I simply do not export the classes / interfaces that are internal. Still
they will all appear in the list of components if I use the karaf
command scr:list. Of course I want see the internal wirings sometimes
but when I look at the whole OSGi framework I think it would be great to
be able to only see the public components at first.
Is this possible somehow?
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
