Thanks guys, FYI pax-jetty did not work but with http and war features there's now have a jetty instance I can hit.
Regards, M. On Wed, Oct 8, 2014 at 11:21 AM, Achim Nierbeck <[email protected]> wrote: > This is because with 3.0.2 the pax web features are now better proxied in > Karaf. > And you really should make use of the http or war feature instead. > > regards, Achim > > 2014-10-08 12:17 GMT+02:00 Marcus Bond <[email protected]>: > >> Sure, I will try to do this.. Notice however that if I add bootFeature >> jetty on 3.01 it will show a Jetty error page (expected) on 8181 but in >> 3.0.2-SNAPSHOT it doesn't. >> >> I will try as you suggested and then try the http feature and get back to >> you. >> >> On Wed, Oct 8, 2014 at 10:37 AM, Jean-Baptiste Onofré <[email protected]> >> wrote: >> >>> Hi, >>> >>> by the way, could you try to put pax-jetty in the boot features instead >>> of jetty (jetty is an "alias" to pax-jetty) ? >>> >>> Regards >>> JB >>> >>> On 10/08/2014 10:45 AM, Marcus Bond wrote: >>> >>>> Hi, >>>> >>>> I've built the 3.0.2-SNAPSHOT from source but in the >>>> assemblies/apache-karaf pom I've added jetty as a bootFeature. The build >>>> works fine but the problem is that when I run it Jetty does not appear >>>> to be available on either port 8181 or port 8080. Is there anything else >>>> required? (Normally there is a jetty error page because there are no >>>> deployed web resources, but this time nothing). >>>> >>>> Regards, >>>> Marcus. >>>> >>> >>> -- >>> Jean-Baptiste Onofré >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >> >> > > > -- > > 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/> > > Software Architect / Project Manager / Scrum Master > >
