JAXB - Property “Value” is already defined. Use to resolve this conflict

Question

Using JAXB to generate XML binding classes.

The schema is based on a set of legacy XML files, and includes this snippet:

Answer 1

The answer lies in making use of JAXB bindings (site-template.xjb):

The XPath expressions locate the nodes and renames it, thereby avoiding the naming conflict.

Using this bindings XML file, the generated Java class ends up having the desired getValueAttribute() (as well as the getValue()).