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 regards, Achim 2016-11-18 17:11 GMT+01:00 Achim Nierbeck <[email protected]>: > There you go ... a crucial missing part I wasn't aware of :) > > I wrote a couple of servlets using bndtools. >> I am now trying to debug them using the instructions in >> http://enroute.osgi.org/appnotes/bndtools-and-karaf.html. > > > I have not the slightest Idea about what bndtools actually does when > "providing" the bundles to Karaf. > I fear lots of the confusion and of course of the failures are due to > bndtools actually providing extra bundles not needed when running inside > Karaf. > > So let's start from scratch then. As I haven't used bndtools for > provisioning, I can't help on that, but I can help you with Karaf ;) > > Is your project capable of producing maven accessible bundles? > Cause the most easiest way of using Karaf is to actually deploy bundles > with a maven coordinate. > > If you use a Vanilla Karaf, you first need to install the http service > (Pax-Web) > via: > > feature:install war > > now you can install a sample servlet application like > > bundle:install -s mvn:org.ops4j.pax.web.samples/whiteboard-blueprint/ > 4.3.2/ > > this will give you a running servlet application on port 8181 > > http://127.0.0.1:8181/ > > you'll find the corresponding integration test at [1]. > > regards, Achim > > [1] - https://github.com/ops4j/org.ops4j.pax.web/blob/master/ > pax-web-itest/pax-web-itest-karaf/src/test/java/org/ops4j/ > pax/web/itest/karaf/WhiteboardKarafTest.java > > > > > > 2016-11-18 16:58 GMT+01:00 Tim Ward <[email protected]>: > >> On 18/11/2016 15:49, Achim Nierbeck wrote: >> >> In combination with the thread on the bnd-tools or osgi-dev I've been >> under the impression that you already tried to >> tweak on certain configurational aspects. >> >> >> Yes, I have been trying for some time to get at various aspects of Jetty >> configuration, and on making no progress at osgi-dev I was finally told >> "oh, if you're using Karaf that's out of scope for this list, try the Karaf >> list". >> >> Therefore I tried to suggest to start with a vanilla instance so we can >> proceed from there. >> >> >> Sorry, I still don't know what you mean by "vanilla instance". >> >> I downloaded and installed Karaf. >> >> I wrote a couple of servlets using bndtools. >> >> I am now trying to debug them using the instructions in >> http://enroute.osgi.org/appnotes/bndtools-and-karaf.html. >> >> If I leave out any of the above I've no longer got anything I can run to >> test whether or not I've managed to switch on Jetty request logging. >> >> For instance this time it's your first statement about which bundles you >> actually did install yourself. As I'm not capable of >> reading mind I have no clue what so ever you have been trying before and >> which bundles have been installed. >> >> >> As per http://enroute.osgi.org/appnotes/bndtools-and-karaf.html plus the >> stuff I've written myself. >> >> regards, Achim >> >> >> 2016-11-18 16:43 GMT+01:00 Tim Ward <[email protected]>: >> >>> On 18/11/2016 15:41, Achim Nierbeck wrote: >>> >>>> I'm not sure which thread I just responded before. >>>> But best to start with a fresh Vanilla Karaf first. >>>> >>> >>> What do you mean by that? - as far as I know I have downloaded and >>> installed Karaf, then installed a couple of tiny bundles of my own so that >>> I've got a servlet to run. How could it be much more "vanilla" than that? >>> >>> >>> I fear with all those tryings of you to somehow configure the server, >>>> it's not possible to >>>> help via mailinglist ... >>>> >>>> regards, Achim >>>> >>> -- >>> >>> Tim Ward >>> >>> >> >> >> -- >> >> 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 >> >> >> >> -- >> Tim Ward >> >> > > > -- > > 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 > > > -- 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
