I have no leads how to fix this 'properly' - or whether it really is a bug. So for the time being, I came up with the following *interim solution: Manipulate the generated sources prior to compiling/CXF Web Service creation.* Accordingly, I've added another plugin to my Maven build process. After code generation (i. e. in Maven's "process-sources" phase), I made said plugin scan certain packages of the generated sources and remove the empty "name"-attribute tokens in question. The plugin is called "maven-replacer-plugin" <https://code.google.com/p/maven-replacer-plugin/> . Here an example "pom.xml"-excerpt for people who want to use aforementioned approach as well. ...<plugin> <groupId>com.google.code.maven-replacer-plugin</groupId> <artifactId>replacer</artifactId> <version>1.5.3</version> <executions> <execution> <phase>process-sources</phase> <goals> <goal>replace</goal> </goals> </execution> </executions> <configuration> <includes> <include>${basedir}/package/path/to/person/source/files</include> <include>${basedir}/package/path/to/other/source/files</include> </includes> <ignoreErrors>false</ignoreErrors> <regex>false</regex> <token>XmlType(name = "",</token> <value>XmlType(</value> </configuration></plugin>... Still: I'm unsure whether I should fill a bug report. And if anyone has *other ideas/solutions*, please share.
-- View this message in context: http://cxf.547215.n5.nabble.com/Question-CXF-generate-Web-Service-issue-when-using-xsd-redefine-tp5746898p5747172.html Sent from the cxf-user mailing list archive at Nabble.com.
