Thanx a lot for your patience. My experience with OSGi frameworks is rather thin so far. I'm trying to apply my knowledge from various app servers to this domain. In fact I'm looking at a migration from Glassfish to a pure OSGi platform.
I'll dig into the material you provided. ----------------------------- Sent from my Android On Dec 20, 2011 4:54 PM, "Sergey Beryozkin-5 [via CXF]" < [email protected]> wrote: > On 20/12/11 14:17, Peter Nerg wrote: > > > Ok, that was a swift answer... > > > > However I'm not sure I follow your suggestion. > > Basically the only thing I want to do is to ramp up the number of > executing > > threads in Jetty. > > Not sure what the default settings are but it doesn't seem to scale much > > beyond 5 concurrent threads from my load test in soap ui. > > > > Is there a better way to configure this on a global level or do I > actually > > have to do it per deployed end point? > > > > If I have to do it per endpoint then I'm not sure I follow your > suggestion > > to /"Consider binding the DOSGI endpoints to HttpService which may help > with > > picking up container-specific HTTP configs"/ > > Do you mean to create BundleActivator and somehow deploy my endpoint to > the > > HTTPService? > > I have not found any examples/documentation on how this would be done. > > Sorry, I was referring to org.apache.cxf.ws.httpservice.context & > org.apache.cxf.rs.httpservice.context properties, see > http://cxf.apache.org/distributed-osgi-reference.html > > This way it is HttpService configuration (have a look at what pax-web > related bundles can do) that will be applied > > > So far I've spent a considerable amount of hours to figure out how to > > perform a configuration that should be a basic task so I'm a bit > confused > > why it must be so complicated. > > > > Well, getting DOSGI picking up the spring context and applying it to the > created endpoints is complicated; so using HttpService can help, IMHO it > is a better strategy anyway, getting the endpoints relying on OSGI > HTTPService. > > Sergey > > > > > -- > > View this message in context: > http://cxf.547215.n5.nabble.com/Fail-to-deploy-webservice-with-httpj-engine-factory-config-tp5088923p5088979.html > > Sent from the cxf-user mailing list archive at Nabble.com. > > > -- > Sergey Beryozkin > > Talend Community Coders > http://coders.talend.com/ > > Blog: http://sberyozkin.blogspot.com > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://cxf.547215.n5.nabble.com/Fail-to-deploy-webservice-with-httpj-engine-factory-config-tp5088923p5089258.html > To unsubscribe from Fail to deploy webservice with httpj:engine-factory > config, click > here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5088923&code=cGV0ZXIubmVyZ0BnbWFpbC5jb218NTA4ODkyM3w5NjEyMzgxMDk=> > . > NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://cxf.547215.n5.nabble.com/Fail-to-deploy-webservice-with-httpj-engine-factory-config-tp5088923p5089740.html Sent from the cxf-user mailing list archive at Nabble.com.
