Its 2.6.2 right now. I think I figured the problem. We had written a custom OOB response provider (with your help) in http://cxf.547215.n5.nabble.com/OAuth-1-0-in-CXF-2-6-2-td5713150i20.html and the response returned from there was being URL encoded. I'll remove that part from the code and check again, and let you know!
-- View this message in context: http://cxf.547215.n5.nabble.com/CXF-Date-marshalling-issue-tp5731091p5731171.html Sent from the cxf-user mailing list archive at Nabble.com.
