Top Methods
org.glassfish.jaxb.runtime.v2.model.runtime

public Interface RuntimeReferencePropertyInfo

extends ReferencePropertyInfo<Type, Class<T>>, RuntimePropertyInfo
Known Direct Implementers
org.glassfish.jaxb.runtime.v2.model.impl.RuntimeReferencePropertyInfoImpl
Imports
org.glassfish.jaxb.core.v2.model.core.ReferencePropertyInfo, java.lang.reflect.Type, java.util.Set

Author
Kohsuke Kawaguchi

Method Summary

Modifier and TypeMethod and Description
public Set<? extends RuntimeElement>
getElements()

Redeclares org.glassfish.jaxb.core.v2.model.core.ReferencePropertyInfo.getElements.

Returns the information about the possible elements in this property.

Inherited from org.glassfish.jaxb.core.v2.model.core.ReferencePropertyInfo:
getAdaptergetDOMHandlergetWildcardgetXmlNameisCollectionNillableisCollectionRequiredisMixedisRequiredref
Inherited from org.glassfish.jaxb.runtime.v2.model.runtime.RuntimePropertyInfo:
elementOnlyContentgetAccessorgetIndividualTypegetRawTyperef

Method Detail

getElementsback to summary
public Set<? extends RuntimeElement> getElements()

Redeclares org.glassfish.jaxb.core.v2.model.core.ReferencePropertyInfo.getElements.

Doc from org.glassfish.jaxb.core.v2.model.core.ReferencePropertyInfo.getElements.

Returns the information about the possible elements in this property.

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.

Annotations
@Override