This tutorial takes the background information on GWT History Management provided in the Managing History and Hyperlinks tutorial and uses it to create an RSS reader application that uses this history mechanism to load initialization parameters. The application that’s built in this tutorial takes the RSS feed URL as a parameter passed to the web app’s URL. You will also learn how to use ROME API, and explore different approaches to displaying application loading (splash) screens.

What is XML? This tutorial provides a brief review of the W3C XML 1.0 Recommendation itself.

The XML SQL database gateway is an engine that accepts an SQL command and returns the ResultSet as an XML document. The gateway uses JDBC in order to connect to the actual database. The gateway also comes with a socket connector. This allows the gateways services to be accessed over a simple socket. Only the socket implementation is provided in this tutorial, the Servlet connector is not provided.

The Hybrid Parser architectural pattern applies to software systems which need to parse documents but are constrained by memory resources and processing power available. The pattern combines the processing advantages concerning execution speed and memory resources of event driven parsers with the programming comfort of a fully-fledged document object model, provided by an object tree parser.

If you’ve ever wanted to access weather reports from your desktop applications, widgets, or web applications, I’ve got some source code that will make it easier than ever to access this weather data from a Java API.

XML and Java can certainly be used to create some very interesting applications from app servers to better searchable websites. However, it is sometimes very difficult to understand where everything really fits. There are web servers, Servlet engines, relational databases, and object databases. Chances are that an XML solution that you have to create will use of one of these prebuilt software pieces. XML development also involves using certain APIs, such as SAX, DOM, Servlets, Swing, RMI, JDBC, and the core Java API.

The applications that you create with Java and XML will rely on the services provided by your Java XML Parser (using DOM or SAX). The information itself might be stored in a variety of persistence engines (object databases, relational databases, file systems, dynamic websites, etc.). The information however that comes out of these persistence storage engines must be converted to XML (if they are not in XML already). Once this is done, you have to be concerned with the material covered in this document. This document outlines the most popular Java XML application categories that are possible in an environment where data is encoded with XML, where web access is ubiquitous and platform independence is a necessity.

There is a lot of hype surrounding XML, and a lot of hype surrounding Java. Together these technologies propose to solve many of the most common (and persistent) general computing problems that have been around for the last 20 years. XML and Java are not revolutionary in the approach to solving these problems of interoperability of code and data across and within platform and application boundaries. Rather, XML and Java provide solutions to these problems by using the most successful strategies and techniques that have been honed and refined over the last 20 years of computing.

This tutorial is a simple introduction to the DOM API.

In order for your programs to access information stored as XML you can use the SAX (Simple API for XML) or the DOM (Document Object Model) APIs. This tutorial will show you how to use SAX to programatically access your information.

SAX (Simple API for XML) and DOM (Document Object Model) were both designed to allow programmers to access their information without having to write a parser in their programming language of choice. By keeping the information in XML 1.0 format, and by using either SAX or DOM APIs your program is free to use whatever parser it wishes. This can happen because parser writers must implement the SAX and DOM APIs using their favorite programming language. SAX and DOM APIs are both available for multiple languages (Java, C++, Perl, Python, etc.).

So both SAX and DOM were created to serve the same purpose, which is giving you access to the information stored in XML documents using any programming language (and a parser for that language). However, both of them take very different approaches to giving you access to your information.

In this tutorial, we will read an XML document and map the content of the XML document to a Java object model; this model can then be view and modified using a Servlet. Also, we will generate an XML document from this Java object model.

In this tutorial, we will read an XML document and map the content of the XML document to a Java object model; this model can then be view and modified using a JFC/Swing application. Also, we will generate an XML document from this Java object model.

In this tutorial, we will create an XML document, the contents of which can be accessed using a JFC/Swing application and from a web browser (via a Servlet). The XML document is a very simplistic representation of an address book which stores the name, email and company name of people. The XML document is written manually, and its structure is known by the Swing application and the Servlet.