Hi Achim
Thanks for your response. Actually I spent quite some time with setting up a jetty.xml but the problem is that if I define an org.eclipse.jetty.server.ServerConnector in jetty.xml on port 8080, I'll receive a port already in use error on startup, since pax-web will create another ServerConnector programmatically in JettyServerImpl (pax-web). Also on port 8080 (org.osgi.service.http).
I also tried setting -Dorg.osgi.service.http.enabled=false assuming that JettyServerImpl would then not create any ServerConnector, but then the ServerConnector I declared in jetty.xml seems like its being initialized, and then closed again by class ServerControllerImpl:
// remove maybe already configured connectors through
// jetty.xml, the config-property/config-admin service is
// master configuration
I also looked at ServerControllerImpl.match() and tried to set up the "name" property of my connector defined in jetty.xml, expecting that in this case the ServerController would recognize my connector and not close it. But also here I had no luck. That's where I decided to post to this group :-)
Silvano