Community
Participate
Working Groups
XmlEnum and XmlEnumValue annotations need the following validation: - XmlEnum.value should match the java type binding of the simple type definition - the type mapped by an enum should be a simple type - the type mapped by an enum *should* be an enumerated simple type, but may not be in certain situations (probably a warning) - the XmlEnumValues should be valid lexical representations of the XmlEnum.value and should map to enumerations of the schema type (if the schema type is enumerated)
XmlEnum needs no further content assist. XmlEnumValue needs the following content assist: - if the schema type resolves to a valid enumerated simple type, the values of the type should be given as completion proposals
Added validation for: - XmlEnum value should map to a simple schema type - XmlEnumValue value should be a valid lexical value for the enum's schema type Added content assist for: - XmlEnumValue value when enum's schema type has enumeration values Chose not to add validation for: - XmlEnum.value should match the java type binding of the simple type definition [The value is always a String type in code. Lexical validation was added instead.] - the type mapped by an enum *should* be an enumerated simple type, but may not be in certain situations (probably a warning) [It is entirely valid to write out xml with enumerated values, even if it isn't a schema constraint.] It is also intentional that no validation was added for *duplicate* XmlEnumValue values, since neither the RI nor MOXy complained in this scenario. Committed for 3.1 M3
