Tools xjc api

Active 3 months ago. Viewed 12k times. I am stuck since yesterday on this problem. I am using Maven 2 on Windows: Apache Maven 2. Gerold Broser Thomas Thomas 5, 5 5 gold badges 28 28 silver badges 45 45 bronze badges. It is linked to this error : stackoverflow. Add a comment. Active Oldest Votes. In case of Exception in thread "main" java. ClassNotFoundException: com. ErrorListener at java.

Adding verbose logging for Maven helped me: mvn -X compile. I had in fact a : Caused by: java. Join the DZone community and get the full member experience. Join For Free. Usage: xjc [-options If dir is specified, all schema files in it will be compiled.

Options: -nv : do not perform strict validation of the input schema s -extension : allow vendor extensions - do not strictly follow the Compatibility Rules and App E. The scripts invoke it as an executable JAR java -jar , as shown in the following excerpts: Windows version xjc. Opinions expressed by DZone contributors are their own. Java Partner Resources. Use this option to force the XJC binding compiler to mark the generated Java sources as read-only. Using this switch causes the generated code to internalize those annotations into the other generated classes.

Suppresses the generation of a file header comment that includes some note and time stamp. Using this makes the generated code more compatible with the diff command. Avoids generating code that relies on any JAXB 2. This will allow the generated code to run with JAXB 2. Be extra verbose, such as printing informational messages or displaying stack traces upon some errors.

Specifies one or more schema files to compile. If you specify a directory, then the xjc command scans it for all schema files and compiles them. Causes all of the generated method signatures to include the synchronized keyword. These options are replaced with the -httpproxy option.

For backward compatibility, these options are supported, but will not be documented and might be removed from future releases. Because the JAXB 2. Therefore, this switch is obsolete and was removed. The -source compatibility switch was introduced in the first JAXB 2.

This switch is removed from future releases of JAXB 2. If you need to generate 1. In general, it is safest to compile all related schemas as a single unit with the same binding compiler switches. Keep the following list of restrictions in mind when running the xjc command. Most of these issues only apply when you compile multiple schemas with multiple invocations of the xjc command.