Questions et reponses d'entretien

� Default bindings can be overridden
� at global scope
� on case-by-case basis
� Customizations include
� names of generated package, classes and methods
� method return types
� class property (field) types
� which elements are bound to classes, as opposed to being ignored
� class property to which each attribute and element declaration is bound

� Customizations can be specified in
� the XML Schema (our focus)
� a binding declarations XML document (not well supported by RI yet)
� The XML Schema must declare
the JAXB namespace and version
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema�
xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
jxb:version="1.0">
� Customization elements are placed in annotation elements
<xsd:annotation>
<xsd:appinfo>
binding declarations
</xsd:appinfo>
</xsd:annotation>

Customizations can be made at four levels
� global
� defined at �top level� in a <jxb:globalBindings> element
� applies to all schema elements in the source schema
and in all included/imported schemas (recursively)
� schema
� defined at �top level� in a <jxb:schemaBindings> element
� applies to all schema elements in the target namespace of the source schema
� definition
� defined in a type or global declaration
� applies to all schema elements that reference the type or global declaration
� component
� defined in a particular schema element or attribute declaration
� applies only to it

� collectionType
� �indexed� (uses array and provides methods to get/set elements) or fully-qualified-java-class-name(must implement java.util.List)
� default is �java.util.ArrayList�
� enableFailFastCheck
� �true� or �false� (default)
� if true, invalid property values are reported as soon as they are set, instead of waiting until validation is requested
� not implemented yet in RI
� generateIsSetMethod
� �true� or �false� (default)
� if true, generates isSet and unSet methods for the property
� underscoreBinding
� �asCharInWord� or �asWordSeparator� (default)
� if �asWordSeparator� , underscores in XML names are removed and words are camel-cased to form Java name
� for example, �gear_shift_knob� goes to �gearShiftKnob�
� bindingStyle (was modelGroupAsClass)
� �modelGroupBinding� or �elementBinding� (default)
� choiceContentProperty
� �true� or �false� (default)
� allows objects to hold one of a number of property choices which may each have a different data type
� enableJavaNamingConventions
� �true� (default) or �false�
� fixedAttributeAsConstantProperty
� �true� or �false� (default)
� if true, �fixed� attributes will be represented as constants
� typesafeEnumBase
� �xsd:string� , �xsd:decimal� , �xsd:float� , �xsd:double� or �xsd:NCName� (default)
� defines field type used to represent enumerated values in generated typesafe enum class
� typesafeEnumMemberName
� �generateName� or �generateError� (default)
� specifies what to do if an enumerated value cannot be mapped to a valid Java identifier
� �generateName� generates names in the form VALUE_#
� �generateError� reports an error

� The syntax for the schemaBindings element is
<jxb:schemaBindings>
<jxb:package [name="package-name"]>
<jxb:javadoc> ... javadoc ... </jxb:javadoc>
</package>
<jxb:nameXmlTransform>
<jxb:typeName prefix="prefix" suffix="suffix"/>
<jxb:elementName prefix="prefix" suffix="suffix"/>
<jxb:modelGroupName prefix="prefix" suffix="suffix"/>
<jxb:anonymousTypeName prefix="prefix" suffix="suffix"/>
</jxb:nameXmlTransform>
</jxb:schemaBindings>
� every element and attribute within schemaBindings is optional