Why do you need to set XmlAccessType.PROPERTY? Simply leaving the
default shouldn't cause any problems since xjc generates the Java
source.
-W
On 23/11/2012, Markward Schubert <markward.schubert_at_gmail.com> wrote:
> Hi Folks!
>
> I am fairly new to XJC and stumbled across a problem. We generate
> Javaclasses from a WSDL+XSD, which generally works fine.
> We also make use of the defaul-value plugin and the accessors plugin.
> These also work fine, but now comes the big "BUT" :-).
>
> The accessors plugin successfully generates the @XmlAccessortype of
> XmlAccessType.PROPERTY, but continues to generate the @XmlElement
> annotations on the fields, resulting in an ugly IllegalAnnotationException,
> claiming that "There are two properties named XYZ".
>
> Is there a way to control, where the @XmlElement is placed, specifically to
> tell that the annotation is to be placed above the getters?
>
> Thank you for any support,
> Markward
>