Well I solved the problem. It was due to my configuration in eclipse. Indeed, I am managing a big project that is split in many projects. given that I'm not using Maven for now, I somehow messed up the runtime dependency and compile time dependency. I was using FATJAR and packaging everything.
So I would say that you were probably right in the end. Because The project that was calling cxf did not have the runtime as a dependency, but a fat jar that i build out of a project where the cxf runtime was a dependency. I don't why exactly it use to work with the 2.5.2 but for the 3.7.4 version did not like it. Now i stop using fat.jar and linking things appropriately, while understanding that some dependencies are runtime and other compile-time. Looking forward to use maven to manage that. I heard that it is the case. Ps: I have used fat.jar for prototyping purpose at the early stage of my project, to rapidly allow my collaborators to try it. -- View this message in context: http://cxf.547215.n5.nabble.com/SOAP-biding-tp5723263p5723273.html Sent from the cxf-user mailing list archive at Nabble.com.
