Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Jean-Baptiste Onofré
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

Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Christian Schneider
I accidently exported all packages. I now changed the maven bundle plugin settings to not export any packages. Still I see no difference. So at least from the display side it can currently not distinguish between internal and public components. Would it make sense to define such a public /

Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Daniel McGreal
Hi, If you declare the @Service to be exported via a class in a non-exported package, would it still be possible to get that class from the service registry by name? Dan. On 17 Feb 2014, at 09:55, Christian Schneider wrote: I accidently exported all packages. I now changed the maven bundle

Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Christian Schneider
Yes. The service registry just holds the properties and the object. So you can retrieve a service that is based on private packages and even use it by means of reflection. At least I am pretty sure it would work :-) Christian On 17.02.2014 10:58, Daniel McGreal wrote: Hi, If you declare the

Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Christian Schneider
I am sure it is possible to do the injection by hand. This means though that I revert all positive aspects of a DI framework. For example in my case I want the commands to share a common DBAccess instance. At the same time I do not want this instance to be public as it is only needed for the

Re: [osgi-dev] Declarative Services: Internal wiring of components in a bundle vs OSGi services

2014-02-17 Thread Peter Kriens
I do not think this is the idea of DS. Spring was invented to handle the byzantine complexity of an average Java application at the time. Trying to wire it all together had become a nightmare because there are ordering issues in initialization. The complexity of apps exploded because the