//Example: code fragment
int[] names;
// XML Serialization Form 1 (Unwrapped collection)
<names> ... </names>
<names> ... </names>
// XML Serialization Form 2 ( Wrapped collection )
<wrapperElement>
<names> value-of-item </names>
<names> value-of-item </names>
....
</wrapperElement>
The two serialized XML forms allow a null collection to be represented either by absence or presence of an element with a nillable attribute.
Usage
The @XmlElementWrapper annotation can be used with the
following program elements:
The usage is subject to the following constraints:
XmlElement,
XmlElements,
XmlElementRef,
XmlElementRefs,
XmlJavaTypeAdapter.See "Package Specification" in jakarta.xml.bind.package javadoc for additional common information.
XmlElement, XmlElements, XmlElementRef, XmlElementRefs
| Modifier and Type | Method and Description |
|---|---|
| public String | |
| public String | |
| public boolean | |
| public boolean |
| name | back to summary |
|---|---|
| public String name() Name of the XML wrapper element. By default, the XML wrapper element name is derived from the JavaBean property name. | |
| namespace | back to summary |
|---|---|
| public String namespace() XML target namespace of the XML wrapper element. If the value is "##default", then the namespace is determined as follows:
| |
| nillable | back to summary |
|---|---|
| public boolean nillable() If true, the absence of the collection is represented by
using | |
| required | back to summary |
|---|---|
| public boolean required() Customize the wrapper element declaration to be required.
If required() is true, then the corresponding generated
XML schema element declaration will have Note that this only affects the schema generation, and not the unmarshalling or marshalling capability. This is simply a mechanism to let users express their application constraints better.
| |