-nnvv 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 com-
piler will not perform any validation, it simply means that it will
Specify one or more external binding files to process. (Each bind-
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 you.
-pp
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.
-hhttttpppprrooxxyy
Specify the HTTP/HTTPS proxy. The format is [user[:password]@]prox-
yHost[:proxyPort]. The old -hhoosstt and -ppoorrtt are still supported by
the RI for backwards compatibility, but they have been deprecated.
Note that the password specified with this option is an argument
that is visible to other users who use the top command, for exam-
ple. For greater security, use -hhttttpppprrooxxyyffiillee, below.
-hhttttpppprrooxxyyffiillee
Specify the HTTP/HTTPS proxy using a file. Same format as above,
but the password specified in the file is not visible to other
users.
-ccllaassssppaatthh
Specify where to find client application class files used by the
and customizations.
-ccaattaalloogg
Specify catalog files to resolve external entity references. Sup-
ports TR9401, XCatalog, and OASIS XML Catalog format. Please read
the XML Entity and URI Resolvers document or the catalog-resolver
sample application.
-rreeaaddOOnnllyy
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.
-nnppaa
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.
-xxmmllsscchheemmaa
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.
-rreellaaxxnngg
Treat input schemas as RELAX NG (experimental, unsupported). Sup-
port for RELAX NG schemas is provided as a JAXB Vendor Extension.
-rreellaaxxnngg-ccoommppaacctt
Treat input schemas as RELAX NG compact syntax(experimental, unsup-
ported). Support for RELAX NG schemas is provided as a JAXB Vendor
Extension.
-ddttdd
Treat input schemas as XML DTD (experimental, unsupported). Support
for RELAX NG schemas is provided as a JAXB Vendor Extension.
-wwssddll
Treat input as WSDL and compile schemas inside it (experimen-
tal,unsupported).
-qquuiieett
Suppress compiler output, such as progress information and warn-
ings.
-vveerrbboossee
Be extra verbose, such as printing informational messages or dis-
playing stack traces upon some errors.
-hheellpp
Display a brief summary of the compiler switches.
-vveerrssiioonn
Display the compiler version information.
Summary of Deprecated and Removed Command Line Options -hhoosstt && -ppoorrtt
These options have been deprecated and replaced with the -hhttttpppprrooxxyy
option. For backwards compatibility, we will continue to support
these options, but they will no longer be documented and may be
removed from future releases.
-uussee-rruunnttiimmee
Since the JAXB 2.0 specification has defined a portable runtime, it
is no longer necessary for the JAXB RI to generate **/impl/runtime
packages. Therefore, this switch is obsolete and has been removed.
-ssoouurrccee
The -source compatibility switch was introduced in the first JAXB
2.0 Early Access release. We have decided to remove this switch
from future releases of JAXB 2.0. If you need to generate 1.0.x
code, please use an installation of the 1.0.x codebase.
-XXllooccaattoorr && -XXssyynncc-mmeetthhooddss
These switches have been disabled for now. We plan on releasing
this functionality as a separate download in the future.
CCoommppiilleerr RReessttrriiccttiioonnss
In general, it is safest to compile all related schemas as a single
unit with the same binding compiler switches.
Please keep the following list of restrictions in mind when running
xjc. Most of these issues only apply when compiling multiple schemas
with multiple invocations of xjc.
+o To compile multiple schemas at the same time, keep the following
precedence rules for the target Java package name in mind:
1. The "-pp" command line option takes the highest precedence.
2. customization
3. If targetNamespace is declared, apply targetNamespace -> Java
package name algorithm defined in the specification.
4. If no targetNamespace is declared, use a hardcoded package
named "generated".
+o It is not legal to have more than one jaxb:schemaBindings> per
namespace, so it is impossible to have two schemas in the same
target namespace compiled into different Java packages.
+o All schemas being compiled into the same Java package must be sub-
mitted to the XJC binding compiler at the same time - they cannot
be compiled independently and work as expected.
+o Element substitution groups spread across multiple schema files
must be compiled at the same time.
07 Aug 2006 xjc(1)