Check out the wsdl_first_https_revised.jar example attached to this Jira issue, the solution here is to either turn off validation of the schema or make a small tweak to the schema to change that attribute to a string instead of an int.
It's quite a bit annoying to modify a provided schema as it may change and thus we have somehow to track its future evolutions. But it works.
This is now fixed (as of yesterday) in the latest 2.2.x snapshots. We've change the schema slightly to a special ParameterizedInt which allows the standard spring patterns or an int (but not "any old string"). We've gone through most of the schemas an updated to them to use the "parameterized" forms when possible to allow the schema validation to work.
See the commit:
That's great. Thanks Dan.