Schema Binding Declarations

<< Global Binding Declarations | Class Binding Declarations >>

USTOMIZATION

VERVIEW

Enumeration Binding Declarations (page 47) for information about local-
ized mapping of

simpleType

definitions to Java

typesafe enum

classes.

typesafeEnumMemberName

can be either

generateError

generate-

Name

. The default value is

generateError

bindingStyle

can be either

elementBinding

, or

modelGroupBinding

The default value is

elementBinding

can be zero or more javaType binding declarations. See

<javaType> Binding Declarations (page 45) for more information.

declarations are only valid in the

annotation

element of the

top-level

schema

element. There can only be a single instance of a

<globalBi-

ndings>

declaration in any given schema or binding declarations file. If one

source schema includes or imports a second source schema, the

<globalBind-

ings>

declaration must be declared in the first source schema.

Schema Binding Declarations

Schema scope customizations are declared with

. The syntax

for schema scope customizations is:

[ <package> package </package> ]
[ <nameXmlTransform> ... </nameXmlTransform> ]*

</schemaBindings>

<package [ name = "packageName" ]

[ <javadoc> ... </javadoc> ]

</package>

[ <typeName [ suffix="suffix" ]
[ prefix="prefix" ] /> ]
[ <elementName [ suffix="suffix" ]
[ prefix="prefix" ] /> ]
[ <modelGroupName [ suffix="suffix" ]
[ prefix="prefix" ] /> ]
[ <anonymousTypeName [ suffix="suffix" ]
[ prefix="prefix" ] /> ]

</nameXmlTransform>

As shown above,

declarations include two subcomponents:

specifies the name of the package and, if

desired, the location of the API documentation for the schema-derived
classes.