Using the JAXB Wizard and Code-Seeder Palette

---

The following topics provide instructions on how access and use data to generate java classes from an XSD or DTD inside the IDE.

What You Need to Know

• About the JAXB Wizard and Code-Seeder Palette

What You Need to Do

• Perform a Typical JAXB Binding Process
• Generate Code Using Code-Seeder Palette (JAXB) Wizard Editor Actions

The following sections provide instructions on how access and use data to generate java classes from an XSD or DTD inside the IDE.

The Java Architecture for XML Binding (JAXB) provides a fast and convenient way to bind XML schemas to Java representations, making it easy for Java developers to incorporate XML data and processing functions in Java applications. As part of this process, JAXB provides methods for constructing, unmarshalling, and marshalling XML content & data using Java language objects. This allows you to leverage the flexibility of platform-neutral XML data in Java applications without having to deal with or even know XML programming techniques. The result is highly portable XML data joined with highly portable Java code that can be used to create flexible, portable applications and Web services.

When using integration solutions, data in web services is received and sent through jax-ws or jax-rpc. By the time the data has been received, it is converted to java classes which makes it easy to access when contained in the message. But not all data enters the system through web services (such as java based integration applications, where data is read from JMS or from the file system) even though there's a similar need to be able to access the data through java classes. The JAXB Wizard enables you to generate java classes from an XSD or DTD inside the IDE. The Code-Seeder Palette's functionality allows you to generate template code in order to marshal, unmarshal, construct JAXB Objects to and from many sources. Sources can be JMS Message, String, or File.

This section covers the following topics:

• Understanding the JAXB Binding Process
  
• Code-Seeder Palette (JAXB) Wizard Editor Palette Actions
  

Performing a Typical JAXB Binding Process

The JAXB APIs and tools are shipped in the jaxb subdirectory of the Java WSDP. This directory contains sample applications, a JAXB binding compiler (xjc), and implementations of the runtime binding framework APIs contained in the javax.xml.bind package. For more information on binding between XML Schema and Java Classes, refer to the following tutorial: http://java.sun.com/javaee/5/docs/tutorial/doc/bnazf.html.

To Perform a Typical JAXB Binding Process

The following steps demonstrate ONE particular way to bind XML schemas and Java representations. Depending on your requirements, the binding process can be achieved in several different ways..

1. Generate JAXB classes. An XML schema is used as input to the JAXB binding compiler to generate JAXB classes based on that schema.
2. Compile JAXB classes. All of the generated classes, source files, and application code must be compiled.
3. Unmarshal XML documents.
   XML documents written according to the constraints in the source schema are unmarshalled by the JAXB binding framework.
   
   Note: JAXB also supports the unmarshalling of XML data from sources other than files/documents, such as DOM nodes, string buffers, and SAX Sources.
   
   
4. Generate content tree. The unmarshalling process generates a content tree of data objects instantiated from the generated JAXB classes; this content tree represents the structure and content of the source XML documents.
5. Validate source XML (optional). The unmarshalling process optionally involves validation of the source XML documents before generating the content tree.
   
   Note: If you modify the content tree in Step 6 (below), you can also use the JAXB Validate operation to validate the changes before marshalling the content back to an XML document.
   
   
6. Process content. The client application can modify the XML data represented by the Java content tree by means of interfaces generated by the binding compiler.
7. Marshal the content tree out to one or more XML output documents. The content may be validated before marshalling. To summarize, using JAXB involves two discrete sets of activities:

• Generate and compile JAXB classes from a source schema, and build an application that implements these classes
  
• Run the application to unmarshal, process, validate, and marshal XML content through the JAXB binding framework
  These two steps are usually performed at separate times in two distinct phases. Typically, there is an application development phase in which JAXB classes are generated and compiled, with a binding implementation being built. That is followed by a deployment phase in which the generated JAXB classes are used to process XML content in an ongoing live production setting.

Generate Code Using Code-Seeder Palette (JAXB) Wizard Editor Actions

The JAXB wizard enables you to generate and compile JAXB classes for a schema, while not requiring a knowledge of the JAXB XML Binding Compiler (xjc) Tool. The wizard also helps in code completion for generated classes. JAXB code generation and compilation is made part of the project's compilation and build task. Once the JAXB Binding is created, the code seeder Palette actions will help you in using the JAXB generated classes in constructing, marshalling, and unmarshalling

Code-Seeder Palette (JAXB) Wizard Editor Actions

The Code-Seeder Palette (JAXB) Wizard contains the following palette actions.

• Constructs JAXB Object
  
• Marshal JAXB Object
  
• Unmarshal JAXB Object
  
  Figure 1-1 Palette Menu

Constructs JAXB Object

The Constructs action generates code to instantiate JAXB objects. This code generation is useful in automating the generation of a series of getter and setter methods, especially when the JAXB object contains a series of nested objects. The code that is generated will not only instantiate the JAXB Object, but will also populate all the nested objects with initial values. This instantiation and population of values and objects can be done by passing a sample XML file. The Sample XML file needs to conform to the XSD/Schema used to generate the JAXB class. When sample XML file is not provided, all the nested JAXB members objects are instantiated.

To Generate Code Using the Constructs JAXB Object

1. Drag and drop the Constructs JAXB Object icon into the IDE editor of an existing project. The Generate JAXB Constructs code dialog box is displayed.
   
   Figure 1-2 JAXB Constructs Object
2. Enter the JAXB class name with the package name to be instantiated/initialized. You can also use the Find... button to search for the class (as shown below).
   Figure 1-3 Find Class Type
3. Enter a sample XML file (if available) for the initialization code to use. Update the auto generated method name if required.
   Figure 1-4 Providing Sample XML File

Assuming the XML file conforms to the schema used in generating JAXB classes, a method will be created (as shown below)
Figure 1-5 Successful Method Created

If the sample XML file is not provided, the code generated will not populate the default values (as shown below).
Figure 1-6 Unpopulated Method

Marshal JAXB Object

The Marshal palette icon action generates template code to marshal a JAXB object. This provides the ability to convert a Java object tree back into XML data. There is no difference between marshalling a content tree that is created manually using the factory methods and marshalling a content tree that is the result of an unmarshal operation. Clients can marshal a Java content tree back to XML data to a java.io.OutputStream or a java.io.Writer. You must know the Class name of the object you are trying to marshal. You can search for the class using the Find... button. The template code can be generated to marshal a JAXB object to a String, OutputStream, File, Writer, or byte array.

To Generate Code Using the Marshal JAXB Object

1. To marshal an existing JAXB class object, drag and drop the JAXB Marshal palette icon to IDE editor. The Generate JAXB Marshal codedialog box is displayed.
   Figure 1-7 JAXB Marshal Object
2. Enter the JAXB object's class name or use the Find... button to search for the class. (as in the Construct's section Figure 1-3)
3. Select the Marshal To option. You can generate the code from a marshal JAXB object to one of String, Writer, OutputStream, JMSTextMessage, or File.
   Figure 1-8 Select Marshal To

The desired method will be generated (as shown below).
Figure 1-9 Marshal Generated Method

Unmarshal JAXB Object

The Unmarshal palette icon action will generate template code to unmarshal a JAXB object. This allows for any global XML element declared in the schema to be unmarshalled as the root of an instance document. The JAXBContext object allows the merging of global elements across a set of schemas (listed in the contextPath). This means that a client application is able to unmarshal XML documents that are instances of any of the schemas listed in the contextPath. You must know the Class name of the object you are trying to unmarshal. Since each schema in the schema set can belong to distinct namespaces, the unification of schemas to an unmarshalling context should be namespace-independent. You can search for the class using the Find... button. The template code can be generated to unmarshal a JAXB object from a String, InputStream, File, Reader, or byte array.

To Generate Code Using the Unmarshal JAXB Object

1. To unmarshal an existing JAXB class object, drag and drop the JAXB Unmarshal palette icon into the IDE editor. The Generate JAXB Unmarshal code dialog box is displayed.
   Figure 1-10 Unmarshal Option
2. Enter the JAXB object's class name or use the Find... button to search for the class. (as in the Construct's section Figure 1-3)
3. Select the Unmarshal From option. You can generate the code to unmarshal a JAXB object from one of String, Reader, InputStream, JMSTextMessage, or File.
   Figure 1-11 Select Unmarshal From

The Unmarshal Method will be generated (as shown below).
Figure 1-12 Unmarshal Method

Previous

This page (revision-8) was last changed on 03-Dec-08 15:17 PM, -0800 by Kevin Hopke.
This page was created on 01-Dec-08 16:04 PM, -0800 by dariopadilla.

More info...