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.
...&lt;plugin&gt; 
&lt;groupId&gt;com.google.code.maven-replacer-plugin&lt;/groupId&gt; 
&lt;artifactId&gt;replacer&lt;/artifactId&gt; 
&lt;version&gt;1.5.3&lt;/version&gt;    &lt;executions&gt;     
&lt;execution&gt;        &lt;phase&gt;process-sources&lt;/phase&gt;       
&lt;goals&gt;          &lt;goal&gt;replace&lt;/goal&gt;       
&lt;/goals&gt;        &lt;/execution&gt;      &lt;/executions&gt;   
&lt;configuration&gt;    &lt;includes&gt;     
&lt;include&gt;${basedir}/package/path/to/person/source/files&lt;/include&gt;   
                             
&lt;include&gt;${basedir}/package/path/to/other/source/files&lt;/include&gt;   
&lt;/includes&gt;    &lt;ignoreErrors&gt;false&lt;/ignoreErrors&gt;   
&lt;regex&gt;false&lt;/regex&gt;    &lt;token&gt;XmlType(name =
"",&lt;/token&gt;    &lt;value&gt;XmlType(&lt;/value&gt; 
&lt;/configuration&gt;&lt;/plugin&gt;...
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.

Reply via email to