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] - https://lists.apache.org/thread.html/cf345ca50e82a2f0ce7b8d664427d89b3ecbf14acd1955645f3c6e07@%3Cuser.karaf.apache.org%3E 2016-11-18 17:18 GMT+01:00 Tim Ward <t...@telensa.com>: > 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 Service >> 873 | Active | 80 | 1.0.0.201611181055 | >> com.telensa.apps.planet.pc.provider >> 874 | Active | 80 | 1.0.0.201611181057 | >> com.telensa.apps.planet.ws.application >> 876 | Active | 80 | 3.2.0 | Apache Felix Http Jetty >> 877 | Active | 80 | 1.1.2 | Apache Felix Servlet API >> 878 | Active | 80 | 2.0.2 | Apache Felix Declarative >> Services >> 879 | Active | 80 | 9.3.8.v20160314 | Jetty :: Utilities >> 880 | Active | 80 | 9.3.8.v20160314 | Jetty :: Utilities :: >> Ajax(JSON) >> 881 | Active | 80 | 2.0.0.201610141744 | >> osgi.enroute.executor.simple.provider >> 882 | Active | 80 | 2.0.0.201610141744 | >> osgi.enroute.logger.simple.provider >> 883 | Active | 80 | 2.0.0.201610141745 | osgi.enroute.web.simple. >> provider >> 884 | Active | 80 | 1.3.100.v20150410-1453 | Coordinator >> 885 | Active | 80 | 2.0.0.201610141744 | osgi.enroute.configurer. >> simple.provider >> 887 | Active | 80 | 1.5.100.v20140428-1446 | Supplemental Equinox >> Functionality >> 888 | Active | 80 | 1.4.8 | Apache Felix EventAdmin > > > all of those services besides 873 and 874 are not needed in the scope of > Karaf ... > ... well maybe 881 to 885 > =============================================================== > > So what do I do now? > > (Services 879 and 880 I put there deliberately because I want to do some > JSON stuff, but any other JSON library would do.) > > > On 15/11/2016 16:27, David Daniel wrote: > > If you are connecting to a running karaf instance as in the second example > and you have enabled the http feature then you are likely using pax web > https://ops4j1.jira.com/wiki/display/paxweb/Advanced+Jetty+Configuration. > But if that is the case then you may get better help on the karaf users > mailing list. > > If you are using enroute locally you are likely running the apache http > service http://felix.apache.org/documentation/subprojects/ > apache-felix-http-service.html You will be able to get better help on > that in the felix users group. > > It is generally the same people on all the lists but I know some people > like to filter so you are more likely to get a response on the appropriate > list. > > On Tue, Nov 15, 2016 at 11:16 AM, Tim Ward <t...@telensa.com> wrote: > >> On 15/11/2016 16:10, David Daniel wrote: >> >>> It is really going to be determined by your httpservice implementation. >>> If you are using Pax-Web like in karaf then there is a jetty.xml file that >>> you can change. If you are using felix http service then many things are >>> configured via the config admin but you will have to look at their >>> documentation and code. If you are just including the jetty bundles then I >>> am not sure. >>> >> >> How do I find out which of those I'm doing? - I'm not knowingly doing any >> of them. >> >> I am running the application in two ways: >> >> (1) From the "Run OSGi" button on the Run page of the bnd.bnd file in >> Eclipse >> (2) From Debug As / Bnd Native Launcher on debug.bndrun, where >> debug.bndrun is created in accordance with >> >> http://enroute.osgi.org/appnotes/bndtools-and-karaf.html >> >> I think I'm more interested in something that works with (2) than I am in >> something that works in (1), if it's going to be different in each case. >> >> >> -- >> Tim Ward >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> > > > > _______________________________________________ > OSGi Developer Mail > listosgi-...@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev > > > > -- > Tim Ward > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
