Description Paul Fullbright 2011-06-02 18:55:08 EDT

Given the following schema:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema 
	xmlns:test="http://example.org/test" 
	xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
	targetNamespace="http://example.org/test">
   
   <xsd:complexType name="root">
      <xsd:sequence>
         <xsd:element name="wrapper" minOccurs="0">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element name="element" type="xsd:string"/>
               </xsd:sequence>
            </xsd:complexType>
         </xsd:element>
      </xsd:sequence>
   </xsd:complexType>
   <xsd:element name="root" type="test:root"/>
</xsd:schema>

and test class:

@XmlType
@XmlRootElement(name = "root")
public class Root {
	
	@XmlElement(name = "element")
	private String element;
}


the element "element" is validated as correct, even though it exists *within* the element "wrapper" and is not a direct child of the "root" type.  When getting content assist for the @XmlElement.name() field, both "element" and "wrapper" are given as choices, even though "wrapper" is the only proper choice in this context.  (Note that if an @XmlElementWrapper(name = "wrapper") is used, then "element" is valid.)