I have a problem where the jaxb2-maven-plugin generates invalid source code when the XSD file contains default values for doubles.
I use the jaxb2-maven-plugin (org.codehaus.mojo) version 1.5:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxb2-maven-plugin</artifactId>
<version>1.5</version>
<configuration>
</configuration>
<executions>
<execution>
<id>analysis_jaxb</id>
<phase>generate-sources</phase>
<goals>
<goal>xjc</goal>
</goals>
<configuration>
<clearOutputDir>false</clearOutputDir>
<schemaFiles>Analysis.xsd</schemaFiles>
<packageName>xx.xx.xx.analysis</packageName>
<generateDirectory>${project.build.directory}/generated-sources/jaxb/analysis</generateDirectory>
<verbose>true</verbose>
</configuration>
</execution>
</executions>
</plugin>
to generate Java Source from the following XSD file:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="MinMax" type="MinMaxType"/>
<xs:complexType name="MinMaxType">
<xs:attribute name="min" type="xs:double" default="-INF" />
<xs:attribute name="max" type="xs:double" default="INF" />
</xs:complexType>
</xs:schema>
The resulting Java file contains this method:
public double getMin() {
if (min == null) {
return -InfinityD; //UNDEFINED
} else {
return min;
}
}
The field -InfinityD
is not defined anywhere.
When using booleans (e.g. <xs:attribute name="minInclusive" type="xs:boolean" default="false" />
) the default values work as expected.
In contrast to this, the plugin org.jvnet.jaxb2.maven2 (maven-jaxb2-plugin) would write Double.POSITIVE_INFINITY
on that problematic line.
Is this simply not supported? Am I missing a parameter?
maven-jaxb2-plugin
. Out of curiosity, why don't you just use themaven-jaxb2-plugin
? Anything you're missing in the plugin? I don't want to persuade you to use my thing, just looking for the constructive feedback. – Twentymaven-jaxb2-plugin
would fail to generate Java files during the build, unfortunately I don't have all the data/stacktraces here to point you in any concrete direction. This lead us to look into alternatives, but the story isn't over yet and we might stick with thejaxb2-maven-plugin
. I'll make sure to file a proper report if we can repeat our issues. – Trager