Hi, Yes, it's fixed on the coming 4.2.3 release.
I plan to submit Karaf 4.2.3 to vote this week. If you can't wait, you can use 4.2.3-SNAPSHOT. I won't be easy on 4.2.2 because it's a fix on the code (not configuration). If you are really on a rush, please ping me directly, I can provide "custom" patched version of jar. Regards JB On 30/01/2019 19:22, abdelb wrote: > Originally fixed this by removing some unneeded cxf features, but deploying > an artefact (that works on older versions of Karaf) has seemed to cause this > issue again. > > I tried John's suggestion but no luck. Is the fix going into 4.2.3 something > I could implement in my 4.2.2 distribution to get it working for now? > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
