Appendix B.2 Support range for JAXB characters

You can specify any character string in the schema document that is the input for schema compiler and in the Java class that is the input for schema generator. Table B-2 describes the support range of the characters of java source input into the schema generator handled in JAXB, and Table B-3 describes the support range of characters of the schema document input into the schema compiler.

Table B-2 Support range of characters of java source input into the schema generator

No.Specification location of any character stringSupport range of the character
1Class name
Method name
Field name
All of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules for the NCName of XML.
2Enumeration constantThe following condition must be fulfilled:
  • Must comprise of alphanumeric characters and underlines.
3prefix element of @XmlNsAll of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules for the NCName of XML.
4Elements of @XmlEnumValue
defaultValue element of @XmlElement or @XmlElementDecl
The following condition must be fulfilled:
  • Must comprise of Unicode Basic Latin and Japanese#1.
5name element of the JAXB mapping annotationAll of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters, underlines, and Japanese#1.
  • Must conform to the syntax rules for the NCName of XML.
6namespace element of the JAXB mapping annotationThe following condition must be fulfilled:
  • Must be an URI character string provided in RFC 2396.#2
7factoryMethod element of @XmlTypeAll of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules for the Java identifier.
8value element of @XmlMimeTypeThe following condition must be fulfilled:
  • Must be a MIME-type text expression.
#1
Characters included in the Unicode Hiragana, Katakana, and CJK Unified Ideographs category.
#2
RFC2732 is not supported (IPv6 not supported).

Table B-3 Support range of characters of the schema document input into the schema compiler

No.Specification location of any character stringSupport range of character
1Attributes of the schema element that specifies the xs:anyURI type (such as the targetNamespace attribute of the xs:schema element)The following condition must be fulfilled:
  • Must be an URI character string provided in RFC 2396.#1
2Attributes of the schema element that specifies the xs:NCName type (such as the name attribute of the xs:element element)All of the following conditions must be fulfilled when the output name is not changed with the custom binding declaration:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules for the NCName of XML.
All of the following conditions must be fulfilled when the output name is changed with the custom binding declaration:
  • Must comprise of alphanumeric characters, underlines, and Japanese#2.
  • Must conform to the syntax rules for the NCName of XML.
3Attributes of the schema element that specifies the xs:QName type (such as the type attribute of the xs:element element)All of the following conditions must be fulfilled:
  • Must be a character string of the QName format.
  • The local name must be within the range of item no. 2.
  • The prefix must comprise of alphanumeric characters and underlines.
4Attribute of the schema element that specifies the xs:string type (such as the fixed or default attribute of the xs:element element, or the fixed or default attribute of the xs:attribute element)
value attribute of the jaxb:typesafeEnumMember element
The following condition must be fulfilled:
  • Must comprise of Unicode Basic Latin and Japanese#2.
5value attribute of the xs:enumeration elementAll of the following conditions must be fulfilled when the enumeration constant is not changed with the custom binding declaration:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules of the Java enumeration constant.
All of the following conditions must be fulfilled when the enumeration constant is changed with the custom binding declaration:
  • Must comprise of Unicode Basic Latin and Japanese#2.
6name attribute of the JAXB element
suffix attribute of the JAXB element
prefix attribute of the JAXB element
parseMethod or printMethod attribute of the jaxb:javaType element
All of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters and underlines.
  • Must conform to the syntax rules for the Java identifier.
7name attribute of the jaxb:package element
ref attribute of the JAXB element
collectionType attribute of the JAXB element
implClass attribute of the jaxb:class element
All of the following conditions must be fulfilled:
  • Must comprise of alphanumeric characters, underlines, and periods (.).
  • Must conform to the syntax rules for the Java package name.
8Element contents of the jaxb:javadoc elementAll of the following conditions must be satisfied:
  • Must be configured of Basic Latin of Unicode and Japanese language#2.
  • Must conform to the syntax rules of the Java command.
#1
RFC2732 is not supported (IPv6 not supported).
#2
Characters included in the category of Unicode Hiragana, Katakana, and CJK Unified Ideographs