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
----------------------------------------------------------------------------------------
56 | Active | 80 | 3.2.0.201605172008 | biz.aQute.remote.agent
895 | Active | 80 | 1.0.0.201611181055 |
com.telensa.apps.planet.pc.provider
896 | Installed | 80 | 1.0.0.201611181622 |
com.telensa.apps.planet.ws.application
898 | Installed | 80 | 9.3.8.v20160314 | Jetty :: Utilities
899 | Installed | 80 | 9.3.8.v20160314 | Jetty :: Utilities ::
Ajax(JSON)
900 | Active | 80 | 2.0.0.201610141744 |
osgi.enroute.executor.simple.provider
901 | Active | 80 | 2.0.0.201610141744 |
osgi.enroute.logger.simple.provider
902 | Installed | 80 | 2.0.0.201610141745 |
osgi.enroute.web.simple.provider
903 | Installed | 80 | 1.3.100.v20150410-1453 | Coordinator
904 | Installed | 80 | 2.0.0.201610141744 |
osgi.enroute.configurer.simple.provider
which is no doubt why the resolver included them in the first place.
karaf@root()> diag
com.telensa.apps.planet.ws.application (896)
--------------------------------------------
Status: Installed
Unsatisfied Requirements:
[com.telensa.apps.planet.ws.application [896](R 896.0)]
osgi.wiring.package; (osgi.wiring.package=javax.servlet)
[com.telensa.apps.planet.ws.application [896](R 896.0)]
osgi.wiring.package; (osgi.wiring.package=javax.servlet.http)
[com.telensa.apps.planet.ws.application [896](R 896.0)]
osgi.wiring.package;
(&(osgi.wiring.package=org.eclipse.jetty.util.ajax)(version>=9.3.0)(!(version>=10.0.0)))
[com.telensa.apps.planet.ws.application [896](R 896.0)] osgi.extender;
(&(osgi.extender=osgi.enroute.configurer)(&(version>=1.0.0)(!(version>=2.0.0))))
[com.telensa.apps.planet.ws.application [896](R 896.0)] osgi.extender;
(&(osgi.extender=osgi.enroute.webserver)(&(version>=1.0.0)(!(version>=2.0.0))))
[com.telensa.apps.planet.ws.application [896](R 896.0)] osgi.contract;
(&(osgi.contract=JavaServlet)(version=3.1.0))
Jetty :: Utilities (898)
------------------------
Status: Installed
Unsatisfied Requirements:
[org.eclipse.jetty.util [898](R 898.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.2.0)))
[org.eclipse.jetty.util [898](R 898.0)] osgi.wiring.package;
(&(osgi.wiring.package=javax.servlet.http)(version>=2.6.0)(!(version>=3.2.0)))
Jetty :: Utilities :: Ajax(JSON) (899)
--------------------------------------
Status: Installed
Unsatisfied Requirements:
[org.eclipse.jetty.util.ajax [899](R 899.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.eclipse.jetty.util)(version>=9.3.8)(!(version>=9.3.9)))
[org.eclipse.jetty.util.ajax [899](R 899.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.eclipse.jetty.util.log)(version>=9.3.8)(!(version>=9.3.9)))
osgi.enroute.web.simple.provider (902)
--------------------------------------
Status: Installed
Unsatisfied Requirements:
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.wiring.package;
(&(osgi.wiring.package=aQute.service.reporter)(version>=1.0.0)(!(version>=2.0.0)))
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.wiring.package;
(osgi.wiring.package=javax.servlet)
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.wiring.package;
(osgi.wiring.package=javax.servlet.http)
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.wiring.package;
(&(osgi.wiring.package=osgi.enroute.servlet.api)(version>=1.3.0)(!(version>=2.0.0)))
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.service;
(objectClass=org.osgi.service.log.LogService)
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.service;
(objectClass=osgi.enroute.servlet.api.ConditionalServlet)
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.service;
(objectClass=osgi.enroute.web.server.cache.Cache)
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.implementation;
(&(osgi.implementation=osgi.http)(&(version>=1.0.0)(!(version>=2.0.0))))
[osgi.enroute.web.simple.provider [902](R 902.0)] osgi.contract;
(&(osgi.contract=JavaServlet)(version=3.1.0))
Coordinator (903)
-----------------
Status: Installed
Unsatisfied Requirements:
[org.eclipse.equinox.coordinator [903](R 903.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.eclipse.osgi.util)(version>=1.1.0)(!(version>=2.0.0)))
[org.eclipse.equinox.coordinator [903](R 903.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=1.1.0)))
osgi.enroute.configurer.simple.provider (904)
---------------------------------------------
Status: Installed
Unsatisfied Requirements:
[osgi.enroute.configurer.simple.provider [904](R 904.0)]
osgi.wiring.package;
(&(osgi.wiring.package=org.osgi.service.coordinator)(version>=1.0.0)(!(version>=2.0.0)))
[osgi.enroute.configurer.simple.provider [904](R 904.0)]
osgi.wiring.package;
(&(osgi.wiring.package=osgi.enroute.configurer.api)(version>=1.0.0)(!(version>=1.1.0)))
[osgi.enroute.configurer.simple.provider [904](R 904.0)] osgi.service;
(objectClass=java.lang.Object)
[osgi.enroute.configurer.simple.provider [904](R 904.0)] osgi.service;
(objectClass=org.osgi.service.cm.ConfigurationAdmin)
[osgi.enroute.configurer.simple.provider [904](R 904.0)] osgi.service;
(objectClass=org.osgi.service.coordinator.Coordinator)
[osgi.enroute.configurer.simple.provider [904](R 904.0)] osgi.service;
(objectClass=org.osgi.service.log.LogService)
karaf@root()>
On 18/11/2016 16:21, Achim Nierbeck wrote:
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
<mailto: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
<http://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
<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
<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
<mailto: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
<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 <mailto:osgi-dev@mail.osgi.org>
https://mail.osgi.org/mailman/listinfo/osgi-dev
<https://mail.osgi.org/mailman/listinfo/osgi-dev>
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
https://mail.osgi.org/mailman/listinfo/osgi-dev
<https://mail.osgi.org/mailman/listinfo/osgi-dev>
--
Tim Ward
_______________________________________________ OSGi Developer
Mail List osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
https://mail.osgi.org/mailman/listinfo/osgi-dev
<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
--
Tim Ward
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
