Ops! Nice to meet you, sorry I didn't recognize and thank you for all the precious work ;-)
2014/1/10 Achim Nierbeck <bcanh...@googlemail.com> > Pax Web that would be me, take a look at the versions available at Pax Web > [1]. > Pax Web 1.x does support Jetty 7, > Pax Web 2.1.x does support Jetty 8 > Pax Web 3 does support Jetty 8 > Pax Web 4 will support Jetty 9 (not released yet) > > With Karaf 3 it will be easier to change versions of Pax-Web due to the > detached feature.xmls > > Regards, Achim > > [1] - https://ops4j1.jira.com/wiki/display/paxweb/Pax+Web > > > 2014/1/10 Cristiano Costantini <cristiano.costant...@gmail.com> > > > Camel and CXF committers regularly contribute to this list and probably > > read this thread so I would appreciate a word on this topic from them on > > this thread (dkulp? cmueller?) > > But who do is responsible for the version of Jetty used by Pax Web used > by > > Karaf? ;-) > > > > I think that ServiceMix community, as user Camel, CXF, Pax Web, should > make > > a tentative to coordinate the other communities in an effort to upgrade > > Jetty version. > > > > Cristiano > > > > > > 2014/1/10 Freeman Fang <freeman.f...@gmail.com> > > > > > exactly, :-) > > > －－－－－－－－－－－－－ > > > Freeman(Yue) Fang > > > > > > Red Hat, Inc. > > > FuseSource is now part of Red Hat > > > > > > > > > > > > On 2014-1-10, at 下午1:55, Achim Nierbeck wrote: > > > > > > > And not to mention pax web :-) > > > > > > > > sent from mobile device > > > > Am 10.01.2014 03:27 schrieb "Freeman Fang" <freeman.f...@gmail.com>: > > > > > > > >> No, at least not for now, we need align jetty version used in CXF > and > > > Camel > > > >> －－－－－－－－－－－－－ > > > >> Freeman(Yue) Fang > > > >> > > > >> Red Hat, Inc. > > > >> FuseSource is now part of Red Hat > > > >> > > > >> > > > >> > > > >> On 2014-1-9, at 下午8:07, jmservicemix wrote: > > > >> > > > >>> Can I upgrade Jetty from the version (seems to be 7.5.4) which > comes > > > >> bundled > > > >>> in ServiceMix? > > > >>> > > > >>> My problem: I am providing SOAP Web service interfaces. My > ServiceMix > > > >> server > > > >>> is behind firewall and it is accessed through Apache proxy. > > > >>> > > > >>> client ----> https://someproxy.public.com/myservice ---> > > > >>> http://servicemix.internal/myservice > > > >>> > > > >>> Apache is configured to set ProxyPreserveHost On. By doing this I > get > > > >> almost > > > >>> working result so that my wsdl > > > >>> > > > >>> https://someproxy.public.com/myservice?wsdl > > > >>> > > > >>> contains correct links like > > > >>> > > > >>> <soap:address location="http://someproxy.public.com/myservice"/> > > > >>> > > > >>> (instead of http://servicemix.internal/myservice) - except that > the > > > >> protocol > > > >>> is wrong (http vs https). The problem is that Jetty 7.5.4 does not > > seem > > > >> to > > > >>> support X-Forwarded-Proto header. > > > >>> > > > >>> As per Jetty documentation > > > >>> > > > > http://wiki.eclipse.org/Jetty/Howto/Configure_mod_proxyX-Forwarded-Proto > > > >>> works from Jetty 9+ ("Proxying SSL on Apache to HTTP on Jetty"). > > > >>> > > > >>> So - is it possible to update to newer Jetty? > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> -- > > > >>> View this message in context: > > > >> > http://servicemix.396122.n5.nabble.com/Upgrading-Jetty-tp5718714.html > > > >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > >> > > > >> > > > > > > > > > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/> >
