Changing the class loader policy to PARENT_LAST should resolve these issues. It helped me fix these issues on WebSphere v8
-- View this message in context: http://cxf.547215.n5.nabble.com/Issue-in-deploying-cxf3-0-2-jar-in-Websphere-8-5-tp5751255p5753369.html Sent from the cxf-dev mailing list archive at Nabble.com.
