Re: [osgi-dev] prototype scope and configuration

On 11/18/2016 1:58 PM, Tim Ward wrote: That sounds a lot like the DS ComponentFactory use case to me. You supply properties to the factory and it spits out a configured instance for you to use. Yeah I agree ComponentFactory seems relevant, and I have played around with it for this use case.

Re: [osgi-dev] prototype scope and configuration

That sounds a lot like the DS ComponentFactory use case to me. You supply properties to the factory and it spits out a configured instance for you to use. Just to confirm, I assume that the standard multiton pattern using factory configurations doesn't help you as the components are stateful

Re: [osgi-dev] prototype scope and configuration

On 11/18/2016 11:45 AM, BJ Hargrave wrote: No. All component instances for the prototype scope service share the same component properties. But each instance represents a different service consumer. This is much the same as a bundle scope service where each component instance has the same

Re: [osgi-dev] prototype scope and configuration

Thanks! Good explanation BJ Hargrave schrieb am Fr., 18. Nov. 2016 um 20:45 Uhr: > No. All component instances for the prototype scope service share the same > component properties. But each instance represents a different service > consumer. This is much the same as a

Re: [osgi-dev] Jetty configuration questions

I want to go back to my previous email and reiterate that it is easiest to pick a framework and work with the tools that are supported by the developers of that framework. Enroute is great with bndtools and gradle but it is really just getting started with maven and has not been around as long as

Re: [osgi-dev] prototype scope and configuration

No. All component instances for the prototype scope service share the same component properties. But each instance represents a different service consumer. This is much the same as a bundle scope service where each component instance has the same component properties but represents a different

Re: [osgi-dev] prototype scope and configuration

I am not aware of that. From my understanding you would use a Component Factory if you need to create a component with a special configuration. Am 18.11.2016 19:40 schrieb "Scott Lewis" : > While reading Neil's description of DS support for prototype scope in > [1], I had

Re: [osgi-dev] How to make packages only visible for some peer bundles?

In Eclipse we have the x-internal directive for that. http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fbundle_manifest.html But IIRC that is Equinox specific and no default OSGi feature. Am 18.11.2016 08:02 schrieb "Christian Schneider"

Re: [osgi-dev] Jetty configuration questions

Hi, doesn't look like the http feature did get installed correctly, as the JavaServlet requirement isn't met. If I'm not wrong you're using DS with your servlets, therefore it's best to install the http-whiteboard feature. Apache Karaf in combination with Pax-Web gives you three different

[osgi-dev] prototype scope and configuration

While reading Neil's description of DS support for prototype scope in [1], I had the following question: Is it possible to associate a configuration with a specific prototype-scoped service instance...declaratively or programmatically? If so, how? Scott [1]

Re: [osgi-dev] Jetty configuration questions

So if I (1) feature:install http (2) comment out the @RequireConfigurerExtender (guessing that whatever this is (it's a line that was in the tutorial I hacked) it ain't ever going to work on Karaf) (3) manually delete from the debug.bndrun everything except the ones I'm deliberately

Re: [osgi-dev] Jetty configuration questions

Sorry, by "didn't get an answer" I meant "didn't get an answer to my problem that solved it". Leaving out the minimal set that you suggests not surprisingly results in things not resolving START LEVEL 100 , List Threshold: 50 ID | State | Lvl | Version| Name

Re: [osgi-dev] Jetty configuration questions

Sorry, but saying this thread [1] is a "didn't get an answer" is not fair. As already tried to point out on the karaf user mailinglist, try to deploy your application without those extra Jetty Bundles! regards, Achim [1] -

Re: [osgi-dev] Jetty configuration questions

I didn't get an answer from the karaf mailing list, essentially I've been pointed back here. The most recent comment was: === Ok, this explains the screw-up: 872 | Active | 80 | 1.0.1 | Apache Felix Log

Re: [osgi-dev] Is there an enroute http service?

On 18/11/2016 15:38, Achim Nierbeck wrote: Hi Tim, 1) is the default configuration for Pax-Web. 2) I don't know this file ... it's not part of Pax-Web 3) ... do you have multiple Jetty instances running with Apache Karaf? I don't know - how do I find out? like did you install some extra

Re: [osgi-dev] Is there an enroute http service?

Ah, I've just realised I've been misleading people. Here is some additional information: (1) org.ops4j.pax.web.cfg contains rg.osgi.service.http.port = 8181 (I don't know why, I didn't put it there.) (2) configuration.json contains "org.osgi.service.http.port" : 8081 (3) Jetty is

Re: [osgi-dev] Is there an enroute http service?

The NPE is caused by the webconsole calling ServletResponse.setContentType(null) The ServletResponse javadoc is not clear on what to do in this case. Should it be allowed? Regards, Christer -- Christer Larsson Makewave, http://www.makewave.com VP EMEA OSGi Alliance, http://www.osgi.org

Re: [osgi-dev] Is there an enroute http service?

I will. On Fri, Nov 18, 2016 at 8:48 AM, Peter Kriens wrote: > You filed a bug at KF? > > Kind regards, > > Peter Kriens > >> On 18 nov. 2016, at 14:43, Benson Margulies wrote: >> >> Unfortunately, the felix web console provokes NPE's in

Re: [osgi-dev] Is there an enroute http service?

You filed a bug at KF? Kind regards, Peter Kriens > On 18 nov. 2016, at 14:43, Benson Margulies wrote: > > Unfortunately, the felix web console provokes NPE's in the KF http > service. I'll stick to the Felix lite alternative. > > On Thu, Nov 17, 2016 at 3:12

Re: [osgi-dev] Is there an enroute http service?

Unfortunately, the felix web console provokes NPE's in the KF http service. I'll stick to the Felix lite alternative. On Thu, Nov 17, 2016 at 3:12 PM, Christer Larsson wrote: > Hi > > The repo is there, but after moving the whole web site to github.io we > discovered that