AnnotationSource, PropertyInfo<java.lang.reflect.Type,java.lang.Class>, ReferencePropertyInfo<java.lang.reflect.Type,java.lang.Class>, RuntimePropertyInfopublic interface RuntimeReferencePropertyInfo extends ReferencePropertyInfo<java.lang.reflect.Type,java.lang.Class>, RuntimePropertyInfo
| Modifier and Type | Method | Description |
|---|---|---|
java.util.Set<? extends RuntimeElement> |
getElements() |
Returns the information about the possible elements in this property.
|
hasAnnotation, readAnnotationdisplayName, getExpectedMimeType, getName, getSchemaType, id, inlineBinaryData, isCollection, kind, parentgetAdapter, getDOMHandler, getWildcard, getXmlName, isCollectionNillable, isCollectionRequired, isMixed, isRequired, refelementOnlyContent, getAccessor, getIndividualType, getRawType, refjava.util.Set<? extends RuntimeElement> getElements()
ReferencePropertyInfoAs of 2004/08/17, the spec only allows you to use different element names when a property is a collection, but I think there's really no reason to limit it there --- if the user wants to use a different tag name for different objects, I don't see why this can be limited to collections.
So this is a generalization of the spec. We always allow a property to have multiple types and use different tag names for it, depending on the actual type.
In most of the cases, this collection only contains 1 item. So the runtime system is encouraged to provide a faster code-path that is optimized toward such cases.
getElements in interface ReferencePropertyInfo<java.lang.reflect.Type,java.lang.Class>Copyright © 2018 Oracle Corporation. All rights reserved.