By default, the XJC binding compiler performs
strict validation of the source schema before
processing it. Use this option to disable strict
schema validation. This does not mean that the binding
compiler will not perform any validation, it simply
means that it will perform less-strict


By default, the XJC binding compiler strictly
enforces the rules outlined in the Compatibility
chapter of the JAXB Specification. Appendix E.2
defines a set of W3C XML Schema features that are not
completely supported by JAXB v1.0. In some cases, you
may be allowed to use them in the “-extension” mode
enabled by this switch. In the default (strict) mode,
you are also limited to using only the binding
customizations defined in the specification. By using
the “-extension” switch, you will be allowed to use
the Overview.


Specify one or more external binding files to
process. (Each binding file must have it’s own -b switch.) The syntax of the external
binding files is extremely flexible. You may have a
single binding file that contains customizations for
multiple schemas or you can break the customizations
into multiple bindings files:

xjc schema1.xsd schema2.xsd schema3.xsd -b bindings123.xjb
xjc schema1.xsd schema2.xsd schema3.xsd -b bindings1.xjb -b bindings2.xjb -b bindings3.xjb

In addition,
the ordering of the schema files and binding files on
the command line does not matter.


By default, the XJC binding compiler will
generate the Java content classes in the current
directory. Use this option to specify an alternate
output directory. The output directory must already
exist, the XJC binding compiler will not create it for


Set the encoding name for generated sources,
such as EUC-JP or UTF-8. If -encoding is
not specified, the platform default encoding is


Specifying a target package via this
command-line option overrides any binding
customization for package name and the default package
name algorithm defined in the specification.


Specify the HTTP/HTTPS proxy. The format is
[user[:password]@]proxyHost[:proxyPort]. The old -host and -port are still
supported by the RI for backwards compatibility, but
they have been deprecated.


Same as the -httpproxy
option, but it takes the
<proxy> parameter in a file, so that you can
protect the password (passing a password in the
argument list is not safe.)


Specify where to find client application class
files used by the <jxb:javaType>
and <xjc:superClass>


Specify catalog files to resolve external entity
references. Supports TR9401, XCatalog, and OASIS XML
Catalog format. Please read the XML Entity and URI
document or the
catalog-resolver sample


By default, the XJC binding compiler does not
write-protect the Java source files it generates. Use
this option to force the XJC binding compiler to mark
the generated Java sources read-only.


Supress the generation of package level
annotations into **/ Using this
switch causes the generated code to internalize those
annotations into the other generated classes.


Supress the generation of a file header comment
that includes some note and timestamp. Using this
makes the generated code more

-target (2.0|2.1)

Avoid generating code that relies on any JAXB
2.1|2.2 features. This will allow the generated code to
run with JAXB 2.0 runtime (such as JavaSE 6.)


treat input schemas as W3C XML Schema (default).
If you do not specify this switch, your input schemas
will be treated as W3C XML Schema.


Treat input schemas as RELAX NG (experimental,
unsupported). Support for RELAX NG schemas is provided
as a Overview.


Treat input schemas as RELAX NG compact
syntax(experimental, unsupported). Support for RELAX
NG schemas is provided as a Overview.


Treat input schemas as XML DTD (experimental,
unsupported). Support for RELAX NG schemas is provided
as a Overview.


Treat input as WSDL and compile schemas inside
it (experimental,unsupported).


Suppress compiler output, such as progress
information and warnings..


Be extra verbose, such as printing informational
messages or displaying stack traces upon some


Display a brief summary of the compiler


Display the compiler version information.


Specify one or more schema files to compile. If
you specify a directory, then xjc will scan it for all
schema files and compile them.


This feature causes the generated code to expose
SAX Locator information about the source XML in the
Java bean instances after unmarshalling.


This feature causes all of the generated method
signatures to include the synchronized keyword.


This feature causes all of the generated code to


Generate an episode file from this compilation,
so that other schemas that rely on this schema can be
compiled later and rely on classes that are generated
from this compilation. The generated episode file is
really just a JAXB customization file (but with vendor


Annotate the @XmlAccessorType
of generated classes with XmlAccessType PROPERTY
instead of FIELD

Let’s block ads! (Why?)

from My Reading List: Read and Unread


Please enter your comment!
Please enter your name here