public interface ReferencePropertyInfo<T,C> extends PropertyInfo<T,C>
PropertyInfo
that holds references to other Element
s.Modifier and Type | Method and Description |
---|---|
Adapter<T,C> |
getAdapter() |
C |
getDOMHandler()
If this property supports the wildcard, returns its DOM handler.
|
Set<? extends Element<T,C>> |
getElements()
Returns the information about the possible elements in this property.
|
WildcardMode |
getWildcard()
If this property supports the wildcard, returns its mode.
|
QName |
getXmlName()
Gets the wrapper element name.
|
boolean |
isCollectionNillable()
Returns true if this property is nillable
(meaning the absence of the value is treated as nil='true')
|
boolean |
isCollectionRequired()
Checks if the wrapper element is required.
|
boolean |
isMixed()
Returns true if this property can hold
String s to represent
mixed content model. |
boolean |
isRequired()
Returns true if this element is mandatory.
|
Collection<? extends TypeInfo<T,C>> |
ref()
List of
TypeInfo s that this property references. |
displayName, getExpectedMimeType, getName, getSchemaType, id, inlineBinaryData, isCollection, kind, parent
hasAnnotation, readAnnotation
Set<? extends Element<T,C>> getElements()
As 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.
Collection<? extends TypeInfo<T,C>> ref()
TypeInfo
s that this property references.
This allows the caller to traverse the reference graph without
getting into the details of each different property type..
If this ReferencePropertyInfo
has a wildcard in it,
then the returned list will contain WildcardTypeInfo
.ref
in interface PropertyInfo<T,C>
QName getXmlName()
boolean isCollectionNillable()
This method is only used when this property is a collection.
boolean isCollectionRequired()
getXmlName()
==null.boolean isMixed()
String
s to represent
mixed content model.WildcardMode getWildcard()
C getDOMHandler()
boolean isRequired()
Adapter<T,C> getAdapter()
getAdapter
in interface PropertyInfo<T,C>
Copyright © 2020 JBoss by Red Hat. All rights reserved.