Invalid @XmlElementRef : Type "class java.lang.Double" or any of its subclasses are not known to this context.

[hamza-zag]

it seems that the element is generating incorrectly "@XmlElementRef" instead of "@xmlelement".

public class AllowedValuesType
    extends AbstractSWEType
    implements Serializable
{
    private final static long serialVersionUID = 1L;
    @XmlElement(type = Double.class)
    protected List<Double> value;
    @XmlElementRef(type = Double.class)
    protected List<Double> interval;
    protected BigInteger significantFigures;
......

XSD:

    <complexType name="AllowedValuesType">
        <complexContent>
            <extension base="swe:AbstractSWEType">
                <sequence>
                    <element maxOccurs="unbounded" minOccurs="0" name="value" type="double"/>
                    <element maxOccurs="unbounded" minOccurs="0" name="interval" type="swe:RealPair"/>
                    <element maxOccurs="1" minOccurs="0" name="significantFigures" type="integer"/>
                </sequence>
            </extension>
        </complexContent>
    </complexType>
<simpleType name="RealPair">
		<restriction>
			<simpleType>
				<list itemType="double"/>
			</simpleType>
			<length value="2"/>
		</restriction>
	</simpleType>

[bghost4]

I Second this issue.

[bertramn]

You will find that doing substitutions on simple data types is probably going to cause a lot more issues. the Java type system is much more limited than the XSD one and hence the JAXB runtime needs all these annotations to figure out how to enforce the additional rules of the XSD model with Java properties. I wrote the plugin to simplify the Java class model where the attribute field would be of a complex type with possible sub type implementations. If you can create a repeatable test failure, I can have a look what happens in the XJC compiler.

[bghost4]

Let me see if I can throw together an example, I'm not using Double, it's a complex type, but it's giving the same subclasses are not known to this context.