Great, thanks JB! On Tue, May 14, 2019 at 1:50 PM Jean-Baptiste Onofré <[email protected]> wrote:
> Hi Eric, > > I'm working on the 4.2.6 preparation. My plan is to submit to vote > during the week end. > > Regards > JB > > On 14/05/2019 13:30, Eric Lilja wrote: > > I saw that KARAF-6279 is now fixed, yay! Awesome! Are we ready for a > > vote of 4.2.6 then or any other blocker/must-have remain? I see 39 > > issues remain open against this 4.2.6, but I assume most if not all will > > be postponed till a later release)? Would be nice to see the release by > > this weekend! > > > > - Eric L > > > > [1] https://issues.apache.org/jira/browse/KARAF-6279 > > > > > > On Sun, May 5, 2019 at 6:31 AM Jean-Baptiste Onofré <[email protected] > > <mailto:[email protected]>> wrote: > > > > Agree, that's the plan. > > > > Regards > > JB > > > > On 04/05/2019 20:34, Eric Lilja wrote: > > > I believe the session issue is a serious one, and it makes sense > to > > > release Karaf 4.2.6 as soon as a fixed Pax-Web is available > > (which I'm > > > hoping is soon). After that, I feel we have a solid and polished > > Karaf > > > on our hands. Assuming the parameter passing issue on WIndows is > > indeed > > > resolved, I don't know of any other major problems. They've been > > dealt > > > with in the previous patch versions of Karaf 4.2.x > > > > > > - Eric L > > > > > > On Sat, May 4, 2019 at 10:25 AM Jean-Baptiste Onofré > > <[email protected] <mailto:[email protected]> > > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > Hi Brock, > > > > > > sorry I missed your message. > > > > > > I'm think it's related to the dual session listener > > registration. It's > > > an issue in Pax Web. I think there's two session handlers. > > > > > > I'm already working on a fix in Pax Web, I will add a test > > related to > > > your use case. > > > > > > Regards > > > JB > > > > > > On 29/04/2019 21:25, Brock Samson wrote: > > > > i have a Karaf-based app that contains a camel route with > > multiple > > > > <cxfEndpoint> instances that look something like this: > > > > > > > > > > > > * <camel-cxf:cxfEndpoint id="Endpoint_1" > > > > continuationTimeout="43200000" > > > > > > > serviceClass="com.teamcenter.esb.service.WebService" > > > > > > address="http://0.0.0.0:8080/myapp/Endpoint1";> > > > > <camel-cxf:inInterceptors> > > > > <beans:bean > > class="com.foo.blah.MyAuthInterceptor"/> > > > > </camel-cxf:inInterceptors> > > > > </camel-cxf:cxfEndpoint> > > > > > > > > <camel-cxf:cxfEndpoint id="Endpoint_2" > > > > continuationTimeout="43200000" > > > > > > > serviceClass="com.teamcenter.esb.service.WebService" > > > > > > address="http://0.0.0.0:8080/myapp/Endpoint2";> > > > > <camel-cxf:inInterceptors> > > > > <beans:bean > > class="com.foo.blah.MyAuthInterceptor"/> > > > > </camel-cxf:inInterceptors> > > > > </camel-cxf:cxfEndpoint>* > > > > > > > > > > > > > > > > while on Karaf 4.1.4, i was able to make all sorts of calls > > to both > > > > endpoints while still on the same session, regardless of > which > > > endpoint the > > > > session was created on. but now the only endpoint i am able > to > > > access is the > > > > one where the session was created. any idea what is causing > > this? > > > camel and > > > > cxf went from 2.20->2.23 and 3.2.1->3.2.7, respectively, so > > that > > > was not > > > > much of a change. jetty on the other had did have a major > > 9.3->9.4 > > > move. > > > > thanks! > > > > > > > > > > > > > > > > -- > > > > Sent from: > > http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > > > > > > > > > > -- > > > Jean-Baptiste Onofré > > > [email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>> > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > > > > > -- > > Jean-Baptiste Onofré > > [email protected] <mailto:[email protected]> > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > >
