I just tried simply creating a folder with your wsdl and pom.xml (of course created src/main/resources and src/main/java dirs), updated the pom.xml to use java 1.6 (basically specified maven-compiler-plugin with source and target 1.6) and ran 'mvn clean package'.
The wsconsume plugin successfully generated the sources.
Try googling on the sax parse exception you get, I this for instance: http://www.mail-archive.com/users@cxf.apache.org/msg02985.html//www.mail-archive.com/users@cxf.apache.org/msg02985.html
In any case this is strange, generally speaking, the wsconsume tooling is a facade over the Sun/Oracle wsimport tooling, so unless you get issues reated to classloading, the same behaviour should be expected...