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 got somehow confused with the runtime dependencies and compile time dependencies.
I would say that you were probably right in the end. Indeed, the entry point project where cxf is ultimately called trough the code of another project, did not have the CXF runtime as a dependency, but a fat jar of that project which however has the cxf runtime as a compile time dependency. I don't know why exactly it use to work with the 2.5.2 version tho. But one thing for sure the 3.7.4 version did not like it. Now i stop using fat.jar and link 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 does it well. 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-tp5723263p5723274.html Sent from the cxf-user mailing list archive at Nabble.com.
