What steps will reproduce the problem? Try with Exchange 2010 over https. Its not working.

What is the expected output? What do you see instead?

Comment deleted

This is a bug with Exchange 2010, IMO. They must have reworked their http processing for SOAP request, because the content type is none forgiving, and must be exact to what they want, not what java defaults to. These are silly differences in parsing the content type, like a space or a semi-colon. I attached a custom soap codecs jar that you must endorse to fix the problem. Sorry for the delay, I have had this done for months, but forgot to distribute it here.