WAS v8.5 > Develop applications > Develop web services > Use JAXB for XML data bindingUse JAXB xjc tooling to generate JAXB classes from an XML schema file
Use Java Architecture for XML Binding (JAXB) xjc tooling to compile an XML schema file into fully annotated Java classes.
Develop or obtain an XML schema file. Use JAXB APIs and tools to establish mappings between an XML schema and Java classes. XML schemas describe the data elements and relationships in an XML document. After a data mapping or binding exists, we can convert XML documents to and from Java objects. We can now access data stored in an XML document without the need to understand the data structure.
To develop web services using a top-down development approach starting with an existing Web Services Description Language (WSDL) file, use the wsimport tool to generate the artifacts for the JAX-WS applications when starting with a WSDL file. After the Java artifacts for the application are generated, we can generate fully annotated Java classes from an XML schema file using the JAXB schema compiler, xjc command-line tool. The resulting annotated Java classes contain all the necessary information the JAXB runtime requires to parse the XML for marshaling and unmarshaling. We can use the resulting JAXB classes within JAX-WS applications or other Java applications for processing XML data.
Best practice: WebSphere Application Server provides JAX-WS and Java Architecture for XML Binding (JAXB) tooling. The wsimport, wsgen, schemagen and xjc command-line tools are located in...
app_server_root/bin
Similar tooling is provided by the Java SE Development Kit (JDK) 6. On some occasions, the artifacts generated by both the tooling provided by WAS and the JDK support the same levels of the specifications. In general, the artifacts generated by the JDK tools are portable across other compliant runtime environments. However, it is a best practice to use the tools provided with this product to achieve seamless integration within the WAS environment and to take advantage of the features that may be only supported in WAS. To take advantage of JAX-WS and JAXB V2.2 tooling, use the tools provided with the application server located in the app_server_root\bin\ directory.
WAS v8.5 supports the JAXB 2.2 specification. JAX-WS 2.2 requires JAXB 2.2 for data binding..
In addition to using the xjc tool from the command-line, we can invoke this JAXB tool from within the Ant build environments. Use the com.sun.tools.xjc.XJCTask Ant task from within the Ant build environment to invoke the xjc schema compiler tool. To function properly, this Ant task requires that you invoke Ant using the ws_ant script.
If we are using the xjc Ant task, use the destdir parameter to specify the destination directory instead of the target option. Specifying the target option when using the xjc Ant task causes an error. gotcha
- Use the JAXB schema compiler, xjc command to generate JAXB-annotated Java classes. The schema compiler is located in the app_server_root\bin\ directory. The schema compiler produces a set of packages containing Java source files and JAXB property files depending on the binding options used for compilation.
- Optional. Use custom binding declarations to change the default JAXB mappings. Define binding declarations either in the XML schema file or in a separate bindings file. We can pass custom binding files using the -b option with the xjc command.
- Compile the generated JAXB objects. To compile generated artifacts, add the Thin Client for JAX-WS with WAS to the classpath.
Results
Now that we have generated JAXB objects, we can write Java applications using the generated JAXB objects and manipulate the XML content through the generated JAXB classes.
Example
The following example illustrates how JAXB tooling can generate Java classes when starting with an existing XML schema file.
- Copy the following bookSchema.xsd schema file to a temporary directory.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="CatalogData"> <xsd:complexType > <xsd:sequence> <xsd:element name="books" type="bookdata" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:complexType name="bookdata"> <xsd:sequence> <xsd:element name="author" type="xsd:string"/> <xsd:element name="title" type="xsd:string"/> <xsd:element name="genre" type="xsd:string"/> <xsd:element name="price" type="xsd:float"/> <xsd:element name="publish_date" type="xsd:dateTime"/> <xsd:element name="description" type="xsd:string"/> </xsd:sequence> <xsd:attribute name="id" type="xsd:string"/> </xsd:complexType> </xsd:schema>- Open a command prompt.
- Run the JAXB schema compiler, xjc command from the directory where the schema file is located. The xjc schema compiler tool is located in the app_server_root\bin\ directory.
app_server_root\bin\xjc.bat bookSchema.xsd
app_server_root/bin/xjc.sh bookSchema.xsd
Running the xjc command generates the following JAXB Java files:
generated\Bookdata.java generated\CatalogdData.java generated\ObjectFactory.java
- Use the generated JAXB objects within a Java application to manipulate XML content through the generated JAXB classes.
Refer to the JAXB Reference implementation documentation for additional information about the xjc command.
Related concepts:
JAXB
Related
Use JAXB for XML data binding
Use JAXB schemagen tooling to generate an XML schema file from a Java class
Use the JAXB runtime to marshal and unmarshal XML documents
Reference:
Web services specifications and APIs
Related information:
JAXB 2.2 Reference implementation