So far, we've primarily looked at XML as a low-level enabling technologyend users won't know if you're using regular properties files or the XML properties files shown in . And when the XML documents we discussed are meant to be shared between apps, those apps are generally data-centric server apps. The last chapter explored examples in which XML was used in a client-server context: RSS and Atom feeds are delivered directly to clients, in those cases RSS and Atom aggregators. (Of course, there are server-based RSS aggregators like News-Gator () and My Yahoo! ().) But that is a limited case tied to the specific vocabularies of RSS and Atom. In this chapter, we'll look at more generic cases of using XML as part of the presentation technology in a web app.

Java Tip

I need to make a few assumptions here. First, I'm going to assume you have read the prior chapters. As with the ROME library used in the last chapter, we're going to be using some of the libraries used prior in this chapter, most significantly, DOM. Second, that you have some familiarity with various web technologies such as HTML, JavaScript, Java servlets, and JavaServer Pages (JSP). Along the same lines, I'm assuming you know how to set up a Java servlet container (such as Apache Tomcat) or can get someone's help to do so. If you want to learn how to write a Java web app, this chapter won't help. So, if you're not at least a little familiar with the above technologies, I'd highly recommend putting this tutorial down, picking up a different one, and coming back here when you're ready. Great tutorials on Java web technology include Java Servlet Programming by Jason Hunter (Oracle) and JavaServer Pages by Hans Bergsten (Oracle).