Learn Java and XML Tutorial

Introduction

In the Java XML Zone you will learn about using XML in your Java applications - start reading to learn how to use Java and the XML DOM.

Play the XSL beginners game

Learn by playing the Understanding the JDOM game.  Read about the Java JDOM and then answer the questions.  See if you can get a 100% score and if not, play it again.

Table of Contents

Learn XALAN - Java Tutorial
XALAN provides APIs for transformation. Xalan-Java (named after a rare musical instrument) fully implements XSL Transformations (XSLT) Version 1.0 and the XML Path Language (XPath) Version 1.0 This tutorial provides a reference covering the usage of the XALAN classes.

30 page javax.xml package class reference
This 30 page reference provides explanations and descriptions for the javax.xml class packages - including SAX, DOM, handlers etc.

TinyLine SVG Minute Toolkit: Optimizing SVG for J2ME
TinyLine SVG Minute Toolkit is targeted at Java developers that want to use SVG for advanced visual messaging and personalization on J2ME platform.

WML Applications using JavaServer Pages (JSP)
This article is about how to use JSPs in the transformation layer, and how to structure the overall framework so that only the transformation layer need be changed to retarget your application from desktop browser to WAP-enabled phone, to whatever other device/application.

SAX2: Producing SAX2 Events
This chapter drills more deeply into how to produce XML events with SAX, including further customization of SAX parsers. A "SAX parser" interface usually works in a kind of "pull" mode: when a thread makes an XMLReader.parse() request, it blocks until the XML document has been fully read and processed. You can also have pure "push" mode event producers. The most common kind writes events directly to event handlers and doesn't use any kind of input abstraction to indicate the data's source; it's not parsing XML text. We discuss several types of such producers later in this chapter.

Responding to SAX Events in JDOM
Using SAX events with JDOM requires: 1. Creating a class that implements org.xml.sax.ContentHandler 2. Instantiating a SAXOutputter object (passing in our ContentHandler class) 3. Passing a JDOM Document to the SAXOutputter output method

Java and XML: SOAP
SOAP is the Simple Object Access Protocol. If you haven't heard of it by now, you've probably been living under a rock somewhere. It's become the newest craze in web programming, and is integral to the web services fanaticism that has taken hold of the latest generation of web development. If you've heard of .NET from Microsoft or the peer-to-peer "revolution," then you've heard about technologies that rely on SOAP (even if you don't know it). There's not one but two SOAP implementations going on over at Apache, and Microsoft has hundreds of pages on their MSDN web site devoted to it. In this chapter, I explain what SOAP is, and why it is such an important part of where the web development paradigm is moving. That will help you get the fundamentals down, and prepare you for actually working with a SOAP toolkit. From there, I briefly run over the SOAP projects currently available, and then delve into the Apache implementation. This chapter is not meant to be the complete picture on SOAP; the next chapter fills in lots of gaps. Take this as the first part of a miniseries; many of your questions at the end of this chapter will be answered in the next.

Java and XSLT: XSLT Processing with Java
Since many of the XSLT processors are written in Java, they can be directly invoked from a Java application or servlet. Embedding the processor into a Java application is generally a matter of including one or two JAR files on the CLASSPATH and then invoking the appropriate methods. This chapter shows how to do this, along with a whole host of other programming techniques.

Firing SAX events from JDOM
Our previous example used a SAX parser to create a document. From our point of view it was single event, from text file to Document object. However, SAX parsers work by raising events when different parts of an XML stream are encountered. All of that was hidden by the call to SAXBuilder.build. Sometimes, though, you want to see those SAX events.

Programming Web Services with XML-RPC: Client-Server Communication
Java was built from the ground up as a network-centric development environment. As a Java developer, XML-RPC offers you an opportunity to extend that foundation in a structured way. Adding XML-RPC to your toolkit makes it easier to integrate a Java application with an application built using another environment or simply to establish lightweight point-to-point communication between Java programs running on different computers. Although XML-RPC goes against the grain of much Java network programming (and even against some of the fundamental principles of object-oriented development), its alternative approach can be useful in many relatively common scenarios.

Interactive Java & XML online tutorial
This 33 page tutorial will introduce you to using Java JDOM and XML - includes SAX, exception handling and more! Includes a test at the end, PDF printable version and sample source code for download. Free!

Client-Side Presentation Logic
There are frequently real-life scenarios where a more proportional sharing of processing between the client and server is necessary. This means that the client will share in the data processing tasks, potentially alleviating the heavy load on the server. In this scenario, the data interchanged between the client and the server is more than HTML. The interchange also contains data that the client can perform processing on. In such a case, the protocol of choice between client and server is still HTTP (as it is still the most widely supported protocol in corporate intranet infrastructures). This means that we must incorporate an extra data delivery mechanism between the 'medium weight' client and the server. XML, as it turns out, is perfect for satisfying this niche in an interoperable manner.

XML Tools for Information Appliances
This chapter focuses on Java, XML, and XSLT technologies for lightweight clients. Lightweight clients are defined as those with more limited resources than traditional clients. The term information appliance is used interchangeably with lightweight client. The obvious devices that fit within this category are personal digital assistants (PDAs), mobile phones, and pagers. However, many other embedded devices and consumer electronics may fit into this category: television set-top boxes, global positioning system (GPS) receivers, thermostats, watches, digital cameras, even Internet appliances such as kitchen stoves, refrigerators, and radios. Non-consumer-oriented devices also can fit in this category, such as industrial automation and control sensors.

Building a WML Application with Enhydra
The first question that you may have is, "What is Enhydra?" Enhydra is an open source application server written entirely in Java. It supports many standards, including XML, HTML, Java Servlets, and JavaServer Pages (JSP)...

WAP Security
Security of applications and computer systems is an issue that, quite rightly, many IT professionals are concerned about. As corporations have utilized technologies, such as remote access, Java and component technologies - the need for mechanisms to secure applications, networks and systems has become more and more important!

JAWAP: the Java Application Framework
Ericsson expects most WAP applications to be developed in the same way as most HTML-rendered sites are today. Because of the benefits to Ericsson of extensive WAP use, it has developed JAWAP. JAWAP is targeted at the low-end WAP developer, but may be used on almost any platform.

Having good SAX with Java
Covers the Simple API for XML, or SAX, interface. It explains why might you use it instead of the DOM, and will get you writing simple applications with SAX, as well as explaining a little bit about where it came from, and where it's going.

Java and the XML DOM
This article is all about using XML with Java to create standalone programs - we'll create a few browsers. Here, the programs we write will be based on the XML DOM, and I'll use the XML for Java (XML4J) packages from IBM alphaWorks