xjc Command-Line Options
JAXB C
OMPILER
O
PTIONS
17
-b file
Specify one or more external binding files to process. (Each binding
file must have its 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. In addition, the ordering
of the schema files and binding files on the command line does not
matter.
-d dir
By default,
xjc
will generate Java content classes in the current
directory. Use this option to specify an alternate output directory.
The directory must already exist;
xjc
will not create it for you.
-p package
Specify an alternate output directory. By default, the XJC binding
compiler will generate the Java content classes in the current direc-
tory. The output directory must already exist; the XJC binding com-
piler will not create it for you.
-proxy proxy
Specify the HTTP/HTTPS proxy. The format is
[user[:pass-
word]@]proxyHost[:proxyPort]
. The old
-host
and
-port
options are still supported by the Reference Implementation for
backwards compatibility, but they have been deprecated.
-classpath arg
Specify where to find client application class files used by the
<jxb:javaType>
and
<xjc:superClass>
customizations.
-catalog file
Specify catalog files to resolve external entity references. Supports
TR9401, XCatalog, and OASIS XML Catalog format. For more
information, please read the XML Entity and URI Resolvers docu-
ment or examine the catalog-resolver sample application.
-readOnly
Force the XJC binding compiler to mark the generated Java sources
read-only. By default, the XJC binding compiler does not write-pro-
tect the Java source files it generates.
-npa
Supress the generation of package level annotations into
**/pack-
age-info.java
. Using this switch causes the generated code to
internalize those annotations into the other generated classes.
-xmlschema
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.
Table 34
xjc
Command-Line Options (Continued)
Option or
Argument
Description
