I believe you are correct. It is the SOAP version. I experienced this as well and as I recall it defaults to one version and certain methods or functionality in the API may not be available for that version. There are a couple of ways to change the default, I think you can even pass in a -d parameter to the JVM. I chose to specify the SOAP version programmatically when instantiating MessageFactory instances:
I think there may have even been a reported bug revolving around this, but I may be mistaken.
Joined: Apr 09, 2010
yes, I do believe that is the right trail to follow, I will have to attempt to force soap client to use 1 soap version.